A small routing detail broke OpenClaw reminder delivery in exactly the wrong place. Here's how I traced it, fixed same-channel delivery, and stopped the agent from claiming success when scheduling had actually failed.
How I split OpenClaw into main and personal agents, gave them separate workspaces, and routed Signal and Teams differently so the system felt more natural to live with.
Why complex enabling work often disappears in large organizations, and why I now think of visibility as part of delivery rather than as a political side quest.
A walkthrough of the Dockerfile I use for OpenClaw: why I extend the base image, what I add for Signal and Teams, and why the order of a few lines matters more than it looks.
How I got OpenClaw talking to Signal and Microsoft Teams from one custom Docker image, and why the base image needed a few extra runtime pieces to make that practical.
The pattern I use to turn SonarQube from passive reporting into an active remediation loop with labels, issues, AI-assisted fixes, and human-controlled pull requests.
Why I chose to run OpenClaw in Docker instead of directly on the host: cleaner dependencies, repeatable rebuilds, durable state, and a setup that plays nicely with tunnels and self-hosted services.
What building CueMarshal taught me about real multi-agent design: role boundaries, permissions, identity, routing, and why orchestration matters more than agent count.
Why I built FireFly around mastery, not streaks: using Bayesian Knowledge Tracing, visual execution, and age-adaptive tutoring to help kids actually understand code.
Why the DORA platform engineering findings rang true to me, and what I have learned from building delivery standards, templates, and paved roads that actually help teams move faster.
