↓ Skip to main content

It’s not so clear cut as it’s made out to be here. Of course writing code should never have been your bottleneck to begin with. What LLMs have done is to remove “I need to write the code” as an excuse.

That has put significant shear on different parts of the system which is a Good Thing. Now we’re tasked with having to figure out how to make those parts better. Before this development, companies could hide their lack of ideas and bad processes behind “it takes the engineers 6 months to ship a feature.” Now they can’t anymore.

https://andrewmurphy.io/blog/if-you-thought-the-speed-of-writing-code-was-your-problem-you-have-bigger-problems

Alper Cugun
Author
Alper Cugun

Related

Knowing what to build, knowing when the system is telling you something, knowing when to cut, knowing when the fast path is the wrong path — these were never just “execution.” They were always the harder parts and to pretend they’re solved by AI is questionable, to say the least.

·104 words
This is an interesting realignment of the org chart. I’m not sure whether we’ll reach that endpoint, but it’s obvious to divide the team into the factors laid out in the article.

·117 words
Claude Code only got good maybe a few months ago, so this only recently started happening, so I assume they will emerge from the spiral eventually.