Last Tuesday I opened Neovim at nine and closed it after one. Four hours. I pressed i twice. The rest was j, k, Ctrl-d, /, gd, Ctrl-o, and a lot of sitting still. An agent had written a 380-line change across six files overnight. My job was to find out whether it was right. I…
Category: AI
Do You Still Read Books?
A developer asked me that on a call in June. Not sarcastically. He asked it the way you would ask someone who still develops film. I had mentioned I picked up the second edition of Designing Data-Intensive Applications. Kleppmann and Riccomini shipped it this spring, nine years after the first one. Six hundred and fifty…
Fable 5 Is Back. The AI Coding Market Already Moved On.
On June 12, the US government told Anthropic to pull Claude Fable 5. Three days after it launched. The order said no foreign nationals could touch it, including Anthropic’s own foreign employees, and since nobody could verify nationality on every request, the model went dark for everyone. API, Claude.ai, Bedrock, all of it. Gone. On…
The New Burnout Comes From Watching, Not Building
A developer with 20 years on the job told me something last week. His old burnout used to make sense. Eight hours of code. Brain fried. Go home. Sleep. Repeat. Predictable. His new burnout is harder to describe. He asks AI to do something. He reads what it produced. Something looks off. He asks again….
Is AI Quietly Contracting the World Economy?
Is AI Quietly Contracting the World Economy? A Quebec translator I read about made roughly six figures in 2023. By late 2025 her work requests had dried up. Total earnings for the year barely cleared €8,000. She is forty-four years old and watching her career end through email, while large language models charge a few…
The Middle Loop Is Where Engineering Actually Lives Now
Someone finally named the thing. There’s a word now for the work I’ve been doing for the last two years without a vocabulary for it. The middle loop. Supervisory engineering. The thing that sits between writing code and shipping it. The thing that didn’t exist before agents started producing code faster than any human could…
Everyone Is an “Engineer” Now, and Nobody Knows What Anyone Does
A CTO’s field guide to the 2026 AI job title theater, with a companion reference guide covering all 40 roles. I have been a CTO for most of my adult life. I have hired, fired, onboarded, mentored, and occasionally been forced to explain to finance why a “Senior Applied Generative AI Engineer II” and a…
The Engineering Age That’s Ending, and the One We Haven’t Named Yet
The best engineers I know write less code than they did two years ago. They ship more. Everyone wants the clean story. AI replaces developers. AI makes developers 10x. Juniors are cooked. Juniors are saved. Pick a side. The reality is messier. Big Tech new grad hires dropped to 7% of all new hires, down…
Vibing Fatigue: Why Tracking AI Usage Is the Wrong KPI
A developer I know got pulled into a “productivity review” last month. Not because their output dropped. Because their AI tool usage was below the team average. Their manager wanted to know why they weren’t using AI for coding enough. Not why their code had fewer bugs. Not why their PRs moved through review faster….
Almost Solved Is the Most Dangerous Phase in Engineering
Everyone agrees AI is transforming how we write code. Adoption is through the roof, productivity metrics look promising, and a growing chorus of voices insists we are months away from this whole thing being “solved.” They are probably wrong. Not because AI is bad, but because “almost solved” is the most dangerous phase in any engineering problem.