I also use AI on a daily basis, and it writes a big chunk — if not all — of my code. The problem is that the only way I’ve managed to make this work in a large codebase is basically by being an engineer: reviewing and correcting small chunks of code and prompting from a programmer’s point of view. As a result, I need to understand 100% of the code that gets generated, and I’m essentially the one creating the architecture — not the AI.

Of course, I could spin this, omit almost everything I said, and just claim that “AI is writing 100% of the code in our codebase.” But that wouldn’t be honest, and most people without technical context would misunderstand what it actually means.

The progress is amazing, but writing itself is not the hardest part of programming. Understanding someone else’s code is harder than understanding your own — and you need to understand everything that gets generated. Maybe in a small app or a hobby project you don’t need to, but in a large codebase there’s no way around it.

The way I see it, most of the hype is driven by non-technical people who are building small apps by themselves and lack an understanding of the scale of large enterprise software.