If you thought the speed of writing code was your problem - you have bigger problems | Debugging Leadership

AI coding tools are optimising the wrong thing and nobody wants to hear it. Writing code was already fast. The bottleneck is everything else: unclear requirements, review queues, terrified deploy cultures, and an org chart that needs six meetings to decide what colour the button should be.

Debugging Leadership
@osxreverser Sad this lacks RSS. Looks like the site is built for it.
@osxreverser extremely on point. Have you ever encountered a team, situation, company, ... where code actually was the bottleneck? Or is it always an: if you think that, you have bigger problems kind-of situation?
@larsborn It's not my article but my personal experience is that code isn't the bottleneck in most places unless the org is too big and dysfunctional. Usually corp bureaucracy and politcs are the real bottlenecks. Creating code is the easy part, the engineering of making a product is the hard part. I guess time will tell what will be the long-term loss or win of all this. I do think it's a stupid idea to replace people instead of using LLMs as force multiplier where it works.
@osxreverser yes, replacing people will backfire quickly, I agree. Also, I like the framing as a multiplier. For me, creating code is/was sometimes the bottleneck. But maybe, I focused much more on cutting red tape and reducing feedback cycles than I realized :-)