Agents Are Here
Late last year I started writing I'm Out On Agents. Agents sucked, the models were good, but there was still something missing between the harnesses and the models. They could write good code, they could do some debugging and exploring, but they were too good a fucking up the whole project to be useful. They could crank out Green Field POC’s like nobody’s business, but they created so much mess in brown field projects that it was easier to chat and edit yourself.
The 7 min read
How To Run 5 Agents In Parallel Feb 2026 Edition
Are developers really running 5 agents in parallel? How the Heck do they keep up with the changes? This seems Impossible.
I was listening to Syntax.fm this morning and heard this question, and thought I’d throw in my take, which is probably pretty similar to Wes and Scott’s.
https://www.youtube.com/watch?v=NrBQI9So5lM&list=PLLnpHn493BHHNUfHN5lDf11UD8jQ5Bpzl&index=1&t=99s
...
Yes, I can review the code and make changes, but who in the world loves reviewing code? Do you love reviewing peers’ PRs? really?
I’m with MeetGor here 100%. reviewing the nuance, not being as involved with the process of creating the architecture design, not solving the problems that arise in development make it hard to effectively review and not turn into LGTM man.
Looks like a great start to a rules file for fastapi.
I have never heard anyone say this. It feels weird to me. The other early return, find and handle errors early all make sense to me, but happy path last is new to me.
Really interesting way to generate a rules file for agentic workflows based on your current repo. John uses gitingest here, looks like a fantastic tool, but probably not useful for most private repos. I’m sure you can replicate the same thing in a private repo wtih a small amount of effort the few times you need to do it. gitingest looks like a great way to pull in some extra context for some open source dependencies that you have though.