Research shows AI makes experienced developers 19% slower, reduces code comprehension by 17%, and trust in AI output is declining. Yet the pressure to be dramatically more productive with AI keeps growing. Here is what the data actually says and how to find your confidence boundary.
The AI Productivity Lie Nobody Wants to AdmitWorking code without architecture predictably collapses. Learn why AI amplifies architectural chaos, how accidental architecture leads to rewrites, and what hexagonal architecture can do to fix it — with practical steps you can take this week.
Your Code Works. Your Architecture Doesn’t.A few weeks ago, I wrote about The Review Bottleneck — how AI-generated code comes with so much confident explanation that we’ve stopped actually reviewing it. We’re not doing more…
AI Code Reviews Are Backwards (Do This Instead)How a simple 50-line notification system spiraled into architectural chaos in 20 weeks—and why AI coding tools now make this descent 10x faster. A cautionary tale every developer will recognize.
A Tale of Accidental Architecture: How 50 Lines Became A Black Friday DisasterSoftware estimation is broken in the AI era. Developers swing between wildly optimistic and pessimistic estimates as AI tools shatter old calibration models. Learn why everyone’s estimates are slipping, what’s really happening behind the scenes, and practical strategies to rebuild estimation skills for AI-augmented development.
Nobody Knows How to Estimate Software Anymore (And It’s Not Your Fault)Last week I spent 3 hours reviewing code that took 20 minutes to write. The AI was faster. The review wasn’t. And I’m starting to realize: that’s the problem. “Less…
The Review Bottleneck: Why AI Explanations Are Making Us Trust Less, Not MoreI walked into the conference room with my laptop to set up the infrastructure demo. Before I could connect to the projector, someone asked me to refill the coffee first….
Working Twice as Hard to Be Seen as Average: Life as a Latino DeveloperAI-generated 847 lines in 12 minutes felt like god mode. But the review took longer than writing it would have. A deep dive into vibe coding, the hidden cost of AI-first development, and why I’m sticking with the terminal + AI pair programming.
Are We Still Developers? The Hidden Cost of Vibe CodingHow I’m staying relevant as a developer in the AI era. Practical habits: writing code by hand, being visible, leading AI agents, keeping a dev journal, automating planning, and taking breaks to skate.
What I’m Doing to Not Become IrrelevantAI agents are shipping code while developers sleep. The job is changing—we are becoming task organizers, configuration engineers, and quality evaluators. How much can we trust AI before our caution becomes a liability? A personal reflection on skill atrophy, the prompt-and-trust workflow, and what it means to be a developer in 2026.
The Developer Identity Crisis