>Writing the code is usually not the bottleneck

I hear this repeated often and it's false.

Writing the code is A bottleneck. Except if by "writing the code" people just mean the mere physical act of typing it in. Which is not what I mean.

But if someone thinks that just the design/architecture decisions take time, and the fleshing out in actual code does not, they're wrong.

Some coders seem to think they're high end architects, and the fleshing out the design is a triviallity that's very fast. Wathing high end coders wrote, e.g. in code session streams or just someone at your office, will show you it's never that fast.

In actual programming practice, even if you know the design end to end, even if it's a 100-line thing, writing it takes time.

Look up how to call those APIs you need. Debug when you inevitable got some of them wrong. Figure out that regex you need to write. Fix the 2-3 things you do wrong on the first pass of the "trivial" algorithm. Add some logic to catch and report errors and handle edge cases. Add tests.

All these are "trivial", but combined can take a couple of hours for something the AI will most of the time spit out correct the first time in a minute. And of course as you write you also explore dozens of decisions that could go either way, even with the same exact design and external interface to your code.

Getting that ready from the LLM within a minute means you can explore alternative designs, handle new issues that occured, add more functionality to make it more usable and smarter , etc, all the while you'd still be writing the original cruder version.

>Using AI is not a goal in itself, so I don’t care about “getting to use AI”. I care about doing my job as efficiently as possible, considering all parts of my job, not just coding.

Not the point. Nobody said AI is a goal in itself.

AI however does speed up the work, and if you take the black-and-white "if AI can't do it all by itself end-to-end without me intervening then I'd rather write everything myself" (what I respond to), then you're not doing your job "as efficiently as possible".