Agents

I was on LinkedIn this morning making a quick post about my experience with Omarchy, and then this showed up in my feed. “Local dev setup makes zero sense to me now.” It’s a comment from Matt Pocock, who we all know by now, the TypeScript educator, creator of the /grill-me skill that half the industry has been grilled by at this point (including myself), with a clip from The Pragmatic Engineer podcast. The post goes on: every dev has a hundred terminals, those terminals should be available to your whole organisation, available from everywhere. So for him that means he’s on a train chatting to his Hetzner box in Discord, and therefore an expensive laptop feels like wasted compute. ...

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. ...

Tools Full comparisons and context in my 2026 AI tech stack post. This is just what you need installed to follow the workflow below. Claude Code If you’re new, start with the cheat sheet and Anthropic best practices. Security — set this up first: Claude Code Security Hooks — 7-layer prompt injection defence, read guards, canary files Lock down your .env and any git-secret files in .claude/settings.local.json before anything else MCP: Context7 — library/API docs on demand DeepWiki — open source repo documentation Skills: ...

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. ...

Introduction In some ways, a lot has changed since my last post, and in other ways, not much has changed. There has been a big shift in the last 12 months, especially toward “agentic engineering” and how we run multi-agent AFK setups vs HITL as we have been. I touched on this in my introduction to the tool I’m working on as well, which, spoiler, is part of my toolchain. Kinda. It’s a WIP… ...

I have not been “AI pilled” yet. (Also, what a stupid term.) While AI has become deeply integrated into my workflow, and I genuinely love having agents run things for me in the background while I focus on other things, I wouldn’t say I’ve had some red pill moment where “I see the truth now” and AI became an essential and daily thing… You see, my morning routine when I start work is the same: I open my terminal of choice (Warp), and I open my IDE of choice (whichever JetBrains one is applicable). And then if the task deems it, I’ll open Junie or Claude inside my IDE. ...

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. ...

🤔 The thing about how much AI agents and tools have improved is that I’m finding myself in a weird spot. I’m always working. Even when I’m not working, I’m planning and brainstorming in Claude Projects so I can use the spec and plan files later in Claude Code. In a recent interview with The Pragmatic Engineer, Mitchell Hashimoto, the founder of HashiCorp said his “new rule for building software: always have an agent running in the background doing something.” (link) ...

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. ...