Live data from Hacker News

Some thoughts on LLMs and software development

martinfowler.com

421–422 of 422 posts

Re: Some thoughts on LLMs and software development

#421

Earlier quoted context omitted.

Google for the Stanford study by Yegor Denisov-Blanch. You might have to pay to access the paper, but you can watch the author’s synopsis on YouTube. For low complexity greenfield projects (best case) they found a 30% to 40% productivity boost. For high-complexity brownfield projects (worst case) they found a -5% to 10% productivity boost. The METR study from a few weeks ago showed an average productivity drop around…

The devil is always in the details with these studies. What did they measure, how did they measure it, are they counting learning the new tool as unproductive time, etc etc etc. I’ll have to read them myself. Regardless, I’ll be sad if it makes most people less productive on average if that’s the scientific truth, but it won’t change the fact that for my specific use case there is a clear time save.

Sure you need to read them yourself to know what conclusions to draw.

In my specific case I felt like I was maybe 30% faster on greenfield projects with AI (and maybe 10% on brownfield). Then I read the study showing a 40 percentage point overestimate on average.

I started tracking things and it’s pretty clear I’m not actually saving anywhere near 30%, and I’d estimate that long term I might be in the negative productivity realm.

Re: Some thoughts on LLMs and software development

#422

Earlier quoted context omitted.

One of the things that has struck me as odd is just how little self-awareness devs have when talking about "skin in the game" with regard to CEO's hawking AI products. Like, we have just as much to lose as they have to gain. Of course a part of us doesn't want these tools to be as good as some people say they are because it directly affects our future and livelihood. No, they can't do everything. Yes, they can do som…

> doesn’t want these tools to be as good as some people say they are No, this is because that would mean AGI. And it’s obviously not that.

What?

I didn't say anything about AGI. Why are you strawmanning this?

Post reply on HN