Colton Voege:
Even if we assume people mean only the actual code writing process is now 10-100x faster, we should still be skeptical of how this maths out. When you write code, how much of your time do you truly spend pushing buttons on the keyboard? It’s probably less than you think. Much of your prime coding time is actually reading and thinking, often while waiting for compiling, a page refresh, or for tests to run. LLMs do not make
rustcgo faster.What LLMs produce is often broken, hallucinated, or below codebase standards. The frequency of these errors go up with the size of the codebase. When that happens you have to re-prompt, which could instantly fix the problem or could be a huge waste of time. Or you can go in and fix the code yourself. But then you’re back to measly 1x engineer status, perhaps worse if you’ve gotten so used to vibe coding you forgot how to code. If you’re “embracing the vibes” and not even looking at the code produced, you’re simply going to hit a productivity wall once the codebase gets large enough. And once you do you’ll have to reckon with the complete lack of standards and proper abstractions.
Although I’ve mostly used AI tools in the context of writing, this has been my experience. It doesn’t actually make you more productive, it just turns a blank page into a page filled with stuff you need to edit. And I’m unconvinced that the process is in any way more efficient than just doing the work yourself.
The obvious exception being when you try to have the AI tools do something that you don’t know how to do. But that typically results in something that you don’t know how to edit because you’re unfamiliar with the tools or concepts. And what good does that do you? Unless you’re happy shipping things of questionable quality, I suppose.
(Via Rui Carmo.)
➝ Source: colton.dev

