Sharing this from the article to hopefully save the post a few downvotes:
Coding was never the bottleneck. Not recently. Not in the last decade. Arguably not since we stopped feeding punchcards into machines.

Sharing this from the article to hopefully save the post a few downvotes:
Coding was never the bottleneck. Not recently. Not in the last decade. Arguably not since we stopped feeding punchcards into machines.

I've long maintained that actually writing code is only a small part of the job. Understanding the code that exists and knowing what code to write is 90% of it.
I don't personally feel that gen AI has a place in my work, because I think about the code as I'm writing it. By the time I have a complete enough understanding of what I want the code to do in order to write it into a prompt, the work is already mostly done, and banging out the code that remains and seeing it come to life is just pure catharsis.
The idea of having to hand-hold an LLM through figuring out the solution itself just doesn't sound fun to me. If I had to do that, I'd rather be teaching an actual human to do it.
The new bottleneck is reviewing the generated slop.
Well now writing/reviewing the code really is the bottleneck.
I meant reviewing the code generated by coworkers 🫤
Was writing code the bottleneck before? Or was it planning, alignment, learning, iteration, testing, etc?
all 18 comments