4 ms·
That METR paper - discussed here two weeks ago: https://news.ycombinator.com/item?id=44522772 https://news.ycombinator.com/item?id=44522772 - has so much sticki
by simonw 1y ago
That METR paper - discussed here two weeks ago: https://news.ycombinator.com/item?id=44522772 https://news.ycombinator.com/item?id=44522772 - has so much sticking power.
It's not a bad paper, but it's also turning into a fantastic illustration of how much thirst there is out there for anything that shows that AI productivity doesn't work.
I just learned there was a 4 minute TV news segment about it on CNBC! https://www.youtube.com/watch?v=WP4Ird7jZoA https://www.youtube.com/watch?v=WP4Ird7jZoA
- timr 1y ago> It's not a bad paper, but it's also turning into a fantastic illustration of how much thirst there is out there for anything that shows that AI productivity doesn't work. Maybe. I think it's a fantastic illustration of anyone doing anything to provide something other than hype around the subject. An actual RCT? Too good to be true! The thirst is for fact vs. speculation, influencer blogposts and self-promotion. That this RCT provided evidence opposing the hype, is, of course, irresistible.
- simonw 1y agoThat's what I liked about the paper: the methodology felt better to me than many other studies. I noted that when I blogged about it (second-to-last paragraph https://simonwillison.net/2025/Jul/12/ai-open-source-productivity/ https://simonwillison.net/2025/Jul/12/ai-open-source-product... )
- pydry 1y agoThe other papers ive seen so far all used toy projects. This paper was the first ive seen that deliberately used realistic projects. I think that part is understated, while the part about the "steep learning curve" has been considerably overstated. Ive watched plenty of good developers with hours of cursor practice, using plenty of relevant context giving clear instructions wasting chunks of 5-10 minutes at a time because 4/5 times claude produced crap that needed to be undone. That story doesnt sell though. Nobody will pay me consulting fees to say it. Hype has more $$$ attached.
- bluefirebrand 1y agoAnyone who is an employee drawing a salary should be extremely hopeful that AI productivity doesn't work. Why should we be eager to find out that some new tech is going to undercut us and replace us, devaluing us even more than we already are?
- deleted 1y ago[deleted]
- simonw 1y agoDo you benefit from open source? Open source packages are the biggest productivity boost of my entire career, at no point did I think "wow, I wish these didn't exist, they're a threat to my livelihood".
- didibus 1y agoI've always thought that I'd probably be paid even more and have the choice of many more jobs if open source didn't exist. Could it be there'd be less jobs because it would have prevented some businesses to bootstrap and stay afloat? That's also possible. And this is really the thing with AI, some think it'll grow the pie, therefore increasing the demand for developers. Some think it'll just shrink the size of the piece of pie that's for developers. If we could predict the former, and be sure of it, I doubt anyone would be against AI. Aside that though, as a developer, you are also concerned with, is this actually making my job better/faster/more-fun. Or am I just forced into an annoying process of using a tool that doesn't help and will just cause more problems I'll have to deal with.
- simonw 1y agoI am so confident that open source expanded the job market. Prior to open source software development was awful. We spent all of our time re-inventing wheels - or, if we were lucky, licensing expensive badly shaped wheels from vendors and crossing our fingers that they would work (because we couldn't fix them if they didn't). As a result, very few companies developed software - it's not worth hiring a software engineer if it takes them six months to deliver that initial login screen. Open source started taking off about 25 years ago, and software productivity skyrocketed. The result was a multi-decade boom in jobs and salaries for us software engineers.
- emp17344 1y agoWell, there aren’t any studies showing AI agents boost productivity, so it’s all we’ve got. It seems like a well-conducted study, so I’m inclined to trust its conclusions.
- simonw 1y agoOne of the articles linked from the OP includes links to such studies: https://theconversation.com/does-ai-actually-boost-productivity-the-evidence-is-murky-260690 https://theconversation.com/does-ai-actually-boost-productiv... - scroll down to the "AI and individual productivity" section, there are two papers there on the "increases productivity" side followed by two others that didn't.
- ofjcihen 1y agoTo be fair that thirst probably comes from people who aren’t seeing the gains the hype would lead you to believe and are reaching into the void to not feel like they’re taking crazy pills. It’s also probably not coming from a place of “I’m scared of AI so I want it to fail” but more like “my complex use case doesn’t work with AI and I’m really wondering why that is”. There’s this desire it seems to think of people who aren’t on the hype train as “against” AI but people need to remember that these are most likely devs with a decade of experience who have been evaluating the usefulness of the tools they use for a long time.
- jsbisviewtiful 1y agoPersonal take, but I think some people also understand that the hype machine around AI is coming from the rich and C-level people. Meanwhile companies are widely and openly axing jobs and or not paying artists, citing AI as the source of their new fortune. Personally, my use of AI in my job has so far not been that fruitful and for something that has so far dramatically underdelivered on its promises of utopian ideas we are instead actively seeing it used to undercut the 99% - and that’s not even getting into the environmental impact or the hellscape it’s made of the Internet.
- archagon 1y agoIt’s telling that there seem to be no AI companies with “boring” CEOs. It’s all glassy-eyed zealots talking about how their product will upend the workforce.
- Terr_ 1y agoTrying out an analogy: The time is the early 2000s, and the Segway™ is being suggested as the archetype of almost all future personal transportation in cities and suburbs. I don't hate the product, there's neat technology there, they're fun to mess with, but... My bullshit sensor is still going off. I become tired of being told that I'm just not using enough imagination, or that I would understand if only I was plugged into the correct social-groups of visionaries who've given arguments I already don't find compelling. Then when somebody does a proper analysis of start/stop distance, road throughput, cargo capacity, etc, that's awesome! Finally, some glimmer of knowledge to push back the fog of speculation. Sure, there's a nonzero amount of confirmation bias going on, but goshdangit at least I'm getting mine from studies with math, rather than the folks getting it from artistic renderings of self-balancing vehicles filling a street in the year 2025.
- didibus 1y agoPersonally, I think this is a disingenuous take. The thirst is for tangible data, the issue is that we've never been able to measure any form of productivity/quality in software development. My team does two person PR reviews for example. We'd go a lot faster if we didn't or even just allowed a single reviewer. Similarly, we have no idea what the quality impact would be if we stopped, and what we gain by doing so. We are we not having a 3 reviewer rule for example, why not, two is an arbitrary number? Unit tests... We'd surely go a lot faster if we didn't bother with them. Teams used to have some dedicated QA members and you'd rely entirely on manual testing. You can push a lot more code out. Was software in the 90s when unit tests and integ tests wasn't used buggier than today's software? Now take AI, what is the impact of its use? It's not even obvious if it reduced the time it takes to launch a feature, my team isn't suddenly ahead of schedule on all our projects, even though we all use Agentic tools actively now. Ask any one of us and "I think it makes us faster" will be the answer. But ask us why we have a 2 person review rule and we'd similarly say: "I think it prevents bugs and improves the code quality". The difference with AI now is that you pay for it, it's not free. Having unit tests or doing a 2 person review is just a process change. AI is something you pay for, so there's more desire to know for sure. And it also is something people would like to know if they can lower their headcount without impacting their competitive edge and ability to deliver fast and with good enough quality. Nobody wants to lower the headcount and find out the hard way.
- thewebguyd 1y ago> the issue is that we've never been able to measure any form of productivity/quality in software development. Yep. It's been a "problem" for decades at this point. Business types constantly trying, and failing, to find some way to measure dev productivity, like they can with other types of office drone work. We've been through Lines of Code, Function Points, various agile metrics, etc. None of these have given business types their holy grail of a perfectly objective measure of productivity. But no one wants to accept an answer of "You just can't effectively measure productivity in software development" because we now live in a data-driven business culture where every little thing must be measured and quantified.
- ajaisjdh 1y agoThere’s literally billions of dollars on the “pro AI side”. What you’re seeing is a thirst for objective reporting. The average person only has the ability to provide anecdotes - many of which are in stark contrast to the narrative pushed by the billionaires pumping AI. I don’t think anyone serious thinks AI isn’t useful in some capacity - but it’s more like a bloom filter than a new branch of mathematics. Magically powerful in specific use cases, but not a paradigm shift.