Ai

A collision is coming that most teams have not noticed yet. On one side you have the workflow your team actually uses. If you run a platform or operations team, it probably looks something like Kanban: pull-based flow, WIP limits, design sessions before implementation, a small number of states that everyone understands. The workflow exists to serve the people. You have spent years tuning it. It works. On the other side you have the lifecycle your AI agent needs. If you are using an agentic framework — Swamp, or something like it — the agent operates through a state machine with enforced transitions, upfront planning, adversarial review gates, and checks that physically prevent skipping steps. The lifecycle exists to constrain the agent. It works. ...

I wrote recently about the difference between easy and simple.1 That post was philosophical. This one is not. This is what it looks like in practice. I have been building an AWS operations toolkit using Swamp. The toolkit investigates outages. It runs daily health checks. It composes nine separate extensions into two workflows that gather data from CloudWatch, X-Ray, EC2, Lambda, and load balancers, then produce an actionable report. This is the machine that builds the machine. Not the code. The system that produces the code and makes sense of the output. ...

We are living through a strange professional silence. Many of us use AI every day while feeling a quiet guilt about it. We worry that by offloading the labor of coding, we are offloading our value as engineers. We reach for the tool because it works. Then we wonder what it means that we needed it. The discomfort is not about the technology. It is the sense that we are moving faster than we can think. ...