> the bottleneck is no longer writing code

The bottleneck has never been the writing of the code. It's all the rest that takes the majority of the time. Of course, it is often the writing which lets you expand your understanding or your awareness of challenges and pitfalls, which then puts you back on the drawing board.

▲

jebarker 4 hours ago | parent | next [-]

This. We’ve just moved the bottleneck from during writing the code to reviewing. The failure mode here is that you can choose to just do a light review since the code “works” but if you had to write the code yourself you would have been forced to consider the design choices and broader implications of the code more.

▲

LelouBil an hour ago | parent | next [-]

AI agents can build a whole app and review PRs better than a lot of people, while having access to more context at once.

Honestly, where did the bottleneck end up now ? It sure isn't simply reviewing, or designing, so where is it ?

	▲	jebarker 18 minutes ago \| parent [-]
		> AI agents can build a whole app and review PRs better than a lot of people Assuming you're comparing to experienced human developers that are good at what they do, then I think you have to define what "better" means here. It's clear that you can get correctly functioning software faster in many cases, but it's not clear that the design will be better in terms of conciseness and readability or that it's as useful as a foundation for building upon later if nobody understands what's going on inside.

▲

skydhash 4 hours ago | parent | prev [-]

The bottleneck they feel during coding is the lack of knowledge. Knowledge of the technical platform and knowledge of the deeper implications of the task’s requirements.

I’ve mentored juniors and the common trait is that they rush to code without understanding, then they spend days trying to fix things. Coding will seem like a real bottleneck for them.

▲

2 hours ago | parent | prev [-]

[deleted]