The October 2025 DynamoDB disruption spread through AWS after a race condition in automated DNS management erased the service’s regional endpoint. Its published cause was an automation defect, not AI-written code. That distinction matters. If we blame every outage on an LLM, we miss the specific mechanisms that made the outage possible. Continue reading →

I have written about Herdr as a place to see all the agents and about why I give spaces, tabs, and panes specific jobs. A multiplexer helps me find the agent that is blocked on a question. It does not tell me whether the agent should still be working on that question at all. Continue reading →

Two developers editing the same service at once is older than Git. One changes an API, the other writes a caller against the old shape. One migration lands, the other assumes the previous schema. The collision may wait until integration, but nobody invented it with coding agents. Continue reading →

Creating a notes repository alongside code repositories enhances project clarity and continuity. It serves as a durable knowledge base for plans, decisions, and team structures, accessible to both human team members and agents. This organized approach minimizes miscommunication and maintains project focus, ensuring everyone stays aligned and informed throughout the development process. Continue reading →

The content discusses the complexities of implementing feature toggles in software development, using three examples: a data pipeline switch, an expedited shipping offer, and a saved filters interface. It emphasizes understanding ownership, failure modes, and scope, and highlights the importance of maintaining clear boundaries and decision-making processes to prevent confusion and errors during development. Continue reading →