The gauge broke: devs felt 20% faster with AI, measured 19% slower (2025)
1–10 of 115 posts
Re: The gauge broke: devs felt 20% faster with AI, measured 19% slower (2025)
#2This may as well have been written in the stone ages, when we were banging AI rocks together.
I just did a ~6 month project in ~2 weeks using a frontier model.
I wouldn't even have attempted this kind work a year ago, with or without the AIs available at the time!
Re: The gauge broke: devs felt 20% faster with AI, measured 19% slower (2025)
#3"19 August 2025" This may as well have been written in the stone ages, when we were banging AI rocks together. I just did a ~6 month project in ~2 weeks using a frontier model. I wouldn't even have attempted this kind work a year ago, with or without the AIs available at the time!
Re: The gauge broke: devs felt 20% faster with AI, measured 19% slower (2025)
#4Re: The gauge broke: devs felt 20% faster with AI, measured 19% slower (2025)
#5AI makes you more productive. This is no longer up for debate. The energy you spend arguing last year's talking points is better spent knuckling down and learning the tools.
Re: The gauge broke: devs felt 20% faster with AI, measured 19% slower (2025)
#6Re: The gauge broke: devs felt 20% faster with AI, measured 19% slower (2025)
#7"19 August 2025" This may as well have been written in the stone ages, when we were banging AI rocks together. I just did a ~6 month project in ~2 weeks using a frontier model. I wouldn't even have attempted this kind work a year ago, with or without the AIs available at the time!
Re: The gauge broke: devs felt 20% faster with AI, measured 19% slower (2025)
#8“16 developers across 246 tasks”
Re: The gauge broke: devs felt 20% faster with AI, measured 19% slower (2025)
#9There was a study that people using the keyboard instead of the mouse felt they were working faster but in fact they were working slower. A perception thing. Users were more engaged when using a keyboard.
Re: The gauge broke: devs felt 20% faster with AI, measured 19% slower (2025)
#10A frontend dev doing tailwind integration for his day job is gonna see very different speedups than someone working in a niche scientific codebase. Taking the average makes about as much sense as taking the average of the speedup from calculators for a mathematician, a farmer, and an elementary school student.