Field notes
Practitioner essays on building production software with AI agents.
Operator-grade reports on the systems, decisions, and economics of shipping software with AI — what worked, what failed, and what changed.
Articles
-

For Five Days His Team Was Accidentally Allowed to Be as Good as They Actually Are
Executive Deck ↗Exec summary ↗Listen ↗My neighbor Bill manages a software team. His company accidentally gave them unlimited AI tokens for a week. They shipped more in seven days than they had in the prior six months. Then finance noticed the bill, and the door closed. Then Bill found a workaround.
-

Why Are You Deprioritizing the Most Important Training Your Org Will Ever Get?
Executive Deck ↗Exec summary ↗Listen ↗You told the board AI would compress delivery cycles by 30%. Then you scheduled the training for 3 PM Friday. This is the private conversation your peers will not have with you.
-

If You Are Tracking Activities Without Outcomes, You Have Already Lost
Executive Deck ↗Exec summary ↗Listen ↗People trained. Workshops delivered. Pilots launched. These are activities, not outcomes. If your transformation dashboard is full of activity metrics and empty of business results, you are measuring your own comfort, not your progress.
-

If Mythos Is Real, Will the Board Wait 24 Months While You Figure It Out?
Executive Deck ↗Exec summary ↗Listen ↗Everyone is talking about Claude and Mythos. Nobody is talking about the fact that your org still cannot ship. The models are not your bottleneck. Your decade-old dysfunction is. And the board is about to notice.
-

Should You Take That Job or Should You Stay
Executive Deck ↗Exec summary ↗Listen ↗A comprehensive guide for developers weighing an offer, leaders trying to retain talent, and executives wondering why their best people keep leaving. The diagnostic that reveals whether an engineering org has actually adopted AI or just bought the tools.




