Top
Best
New

Posted by phire 7 days ago

Writing Code Was Never the Bottleneck(ordep.dev)
767 points | 385 commentspage 8
conartist6 4 days ago|
My philosophy is dirt simple:

I am the pointy end of the spear.

bobsmooth 4 days ago||
I'm less concerned with professionals using LLMs to code and more excited by the idea of regular people using LLMs to create programs that solve their problems.
farzadmf 4 days ago||
Wish the blog had an RSS feed
desio 4 days ago||
Maybe true, but not true enough.
albertojacini 4 days ago||
The title says it all
tropicalfruit 4 days ago||
bottom line is only thing that matters in the end
dxroshan 4 days ago||
The author doesn't give any arguments to support his claim.
revskill 4 days ago||
Nan, it depends on quality of data you trained the bot.
2d8a875f-39a2-4 4 days ago||
The author puts the BLUF: "The actual bottlenecks were, and still are, code reviews, knowledge transfer through mentoring and pairing, testing, debugging, and the human overhead of coordination and communication."

They're not wrong, but they're missing the point. These bottlenecks can be reduced when there are fewer humans involved.

Somewhat cynically:

code reviews: now sometimes there's just one person involved (reviewing LLM code) instead of two (code author + reviewer)

knowledge transfer: fewer people involved means this is less of an overhead

debugging: no change, yet

coordination and communication: fewer people means less overhead

LLMs shift the workload — they don’t remove it: sure, but shifting workload onto automation reduces the people involved

Understanding code is still the hard part: not much change, yet

Teams still rely on trust and shared context: much easier when there are fewer people involved

... and so on.

"Fewer humans involved" remains a high priority goal for a lot of employers. You can never forget that.

mdavid626 4 days ago|
Slowly it’s getting time to become a goose farmer. Enough of this AI shit.
More comments...