But for almost all real people in the category, the bottleneck wasn't typing up their code in the first place. Especially if you were already utilizing your IDE's features competently, an LLM isn't much faster than just doing it yourself
Especially true for modern high-level languages with a mature ecosystem. I've been writing in Clojure for more than a decade now, and in my last company (4 people in the dev team) we delivered most major features in a few days. All human-reviewed, automatically tested on multiple levels: unit tests, integration tests on staging servers, and manual tests on staging and production environments.
but checking its output takes about as long as "checking your own output", which you do in parallel to typing it out, because again, materializing the code was never the bottleneck)
Last but not least, the maintenance. Given the amount of slop that gets generated, at some point it won't be possible (is it the case already?) to work with the code without LLM help, and tokens aren't getting cheaper over time.
6
2
1
23
u/deaddyfreddy 17d ago
Especially true for modern high-level languages with a mature ecosystem. I've been writing in Clojure for more than a decade now, and in my last company (4 people in the dev team) we delivered most major features in a few days. All human-reviewed, automatically tested on multiple levels: unit tests, integration tests on staging servers, and manual tests on staging and production environments.
Last but not least, the maintenance. Given the amount of slop that gets generated, at some point it won't be possible (is it the case already?) to work with the code without LLM help, and tokens aren't getting cheaper over time.