C.A.S.T full multi-repo demo

Two Repos, Twenty Minutes, One Nosy Agent

A few weeks ago I had my agents continue work on CAST, and after some progress I handed two tickets to a team of five software agents and went away to make coffee. Twenty minutes later both tickets were closed, the code was merged, and the only things I’d typed were two tracker commands and some answers to questions. Great success right? Then I read the transcripts… But before we get to that If you are just joining me, I’ve been building a thing called CAST for a while now. Collaborative Autonomous Software Team. The pitch is small: tickets are the unit of work, a product-manager agent refines them, a developer agent builds them, a reviewer agent checks the result against the acceptance criteria, and a human merges. Nothing moves between those states unless a label changes on the ticket, and every label change is an event the next agent wakes up on. ...

November 8, 2026 · 12 min · 2394 words · map[email:me@wynandpieters.dev name:Wynand Pieters]
C.A.S.T full lifecycle demo

C.A.S.T Progress: Five Roles, One Ticket, Zero Human Coding

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

September 4, 2026 · 18 min · 3660 words · map[email:me@wynandpieters.dev name:Wynand Pieters]
C.A.S.T first integration test

C.A.S.T Progress: First Blood

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

May 28, 2026 · 8 min · 1505 words · map[email:me@wynandpieters.dev name:Wynand Pieters]
Cover image for Maybe Software Engineering Should Be Regulated. I Can't Decide If That Terrifies Me.

Maybe Software Engineering Should Be Regulated. I Can't Decide If That Terrifies Me.

Trigger warning: this is part rant, part genuine exploration, and entirely my opinion. As usual. Also; research heavy. I wanted this to be informed. I’ve been thinking about this one for a while. In a previous post I argued that not everyone who writes code is an engineer, and that the title carries expectations. In another I complained about the lack of standards in an industry that rewards speed and hype over depth. And more recently I got on my soapbox about fundamentals mattering — about how the people who actually understood the machines they worked on are slowly dying off, and what we’re being left with instead. ...

April 20, 2026 · 19 min · 3899 words · map[email:me@wynandpieters.dev name:Wynand Pieters]
Cover image for C.A.S.T.

The Future of AI Coding is Directing. Let Me Introduce You to Your C.A.S.T.

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

April 9, 2026 · 9 min · 1797 words · map[email:me@wynandpieters.dev name:Wynand Pieters]
Cover image for The over-engineering trap

The over-engineering trap

🧩 I fell into a trap. One I’m often warning others not to fall into. Two of them, actually. 💻 The solution I’m building for one client isn’t necessarily a hard problem. There are existing solutions, but we want a simple MVP at lowest cost, so most paid services are off the table. With our custom integration needs, we decided to roll most of it ourselves. No, this wasn’t the trap. ...

March 6, 2025 · 2 min · 378 words · map[email:me@wynandpieters.dev name:Wynand Pieters]