
Engineers are picking sides in the AI coding fight as if the outcome is still up for grabs. It isn't. The work is just as complex as it ever was, but the need for a human to wade through it is being stripped out, and the transition is already done. If you write code for a living, arguing about vibe coder garbage won't save your career. Adapting, teaching the next lot how to do it properly, or jumping before the redundancy hammer drops might.
Created: 13/06/2026

The first in an AI coding series built on what actually works day to day, not best-practice theory. The argument is simple and uncomfortable: stop slotting AI into the workflow you already have, and rebuild the workflow around it instead. First target is documentation, where the old human habits actively make AI coding worse, and where the AI, not you, should be writing and maintaining the docs.
Created: 27/05/2026

AI coding agents like Claude Code and Codex will happily generate unreadable garbage, but that used to be expensive mainly because cleaning it up cost developer time. Now you can refactor bad code fast and cheap. The risk that actually bites is spaghetti infrastructure: the hosting, databases, auth, third-party APIs and AI providers your vibe coded product is wired into. Those are hard to leave, fail independently, multiply your security exposure, and can price you out as you grow. If your time is limited, ignore the code and fix the infrastructure.
Created: 26/05/2026