Previous posts for context: The Future of AI Coding is Directing and C.A.S.T Progress: First Blood Last time I had one event flowing from a ticket board to a NATS topic. That was the plumbing. This time the plumbing has something running through it: a ticket goes in one end as a one-line wish, and a reviewed, merged, cleaned-up branch comes out the other. No human types a line of code in between. ...
Previous post for context: The Future of AI Coding is Directing. Let Me Introduce You to Your C.A.S.T. Also, this banner was generated by ChatGPT and whatever model they are using at the moment, and I’m kinda impress, NGL. When I wrote about C.A.S.T last month, the design was solid but unproven. I had a SPEC, ADRs, hire/fire scripts, and a lot of conviction. What I didn’t have was a single event flowing from a ticket board to a NATS topic to a waiting agent. ...
Do trust and accountability go hand in hand? This is something I’ve been chewing on over the weekend. And I don’t know really, but here’s where I’m coming from. One of my side projects at PiForge at the moment is building a system around Agentic Engineering using team lead principles I’ve honed over years, and applying how human teams communicate and organize over the SDLC to agents (i.e. start with a spec, write tickets on a kanban board, grab the next highest priority, work till done, test, PR, release, document). ...
Previous post for context: Two AI Agents Walk Into a Codebase If you look at social media, everyone will tell you that most people are still using AI like a very fast keyboard. You write what you want, it writes the code, you review it, you move on. Faster, sure. But you’re still in the driver’s seat for every line, every file, every decision. They will also tell you that the future is not that. The future is swarms of AI agents doing the work of 100s of people. And I mostly agree. The shift that’s actually happening — and I say this as someone who’s spent the last month living inside it — is from writing code to directing agents. ...
That’s the punchline and the problem. I’ve run into these two similar scenarios which have had me stumped and annoyed. In one, I’m running Claude Code in both GoLand and PyCharm, trying to integrate one project’s API with another project’s GRPC service. In the other, I have a Scala library that needs updates, and then multiple services that depend on that library. The hiccup: each instance is completely unaware of the other’s existence. ...