The Code Nobody Understands Is Already in Production
AI writes code faster than ever. But there's a trade-off almost nobody talks about: we're exchanging development speed for operational opacity. And that exchange isn't free.
AI writes code faster than ever. But nobody talks about what happens next: who operates that code when it fails, who diagnoses it at 3 AM, who verifies it deserves to be in production. This series explores the industry's biggest blind spot right now: we're generating systems nobody fully understands, with heuristics nobody transmits, and without infrastructure to verify what we produce. Code is getting cheaper. Judgment is what's expensive.
5 articles in this series
AI writes code faster than ever. But there's a trade-off almost nobody talks about: we're exchanging development speed for operational opacity. And that exchange isn't free.
Senior engineers resolve incidents faster, but they can't explain how they do it. Gary Klein discovered the same thing with firefighters in 1984: tacit knowledge is built through experience and can't be easily articulated. This matters now more than ever.
Dario Amodei says AI will replace engineers in 6-12 months. Jensen Huang says we shouldn't learn to code. I've been thinking about this for months. I don't have all the answers, but I do have a stance.
When a senior hoards knowledge in their head, the team is left without a safety net. With AI accelerating code creation, sharing context is no longer a nice-to-have -- it's a critical responsibility.
Anthropic separated the agent that generates from the one that evaluates and quality skyrocketed. That pattern describes the future of software engineering: generation is commodity. Verification is craft.
The series keeps growing. Subscribe to the newsletter so you don't miss the next installments.
Join other engineers who receive reflections on career, leadership, and technology every week.