6 ms·
> AI users were actually 19% slower, but they thought they were 20% faster. I don't know who made those numbers up, but for me... I can almost certainly guaran
by AmazingTurtle 3mo ago
> AI users were actually 19% slower, but they thought they were 20% faster.
I don't know who made those numbers up, but for me... I can almost certainly guarantuee, I have never been so relaxed before. Doing multiple paid projects simultaneously due to AI, still leaning back, customer's are happy. I can confidently say: if you know how to leverage it properly, you can be both more efficient and relaxed at the same time. I'd also argue, if you use a combination of SOTA models to code and review and put in some own thoughts, too, then code is also GG.
- lionkor 3mo agoThis is the source of that information: https://metr.org/blog/2025-07-10-early-2025-ai-experienced-os-dev-study/ https://metr.org/blog/2025-07-10-early-2025-ai-experienced-o... The updated METR study on this gives different results, but they should still be quite sobering.
- annon 3mo agoThey didn't even give the correct reference in the footer, calling it Meter RCT trial. This is just AI spam.
- deleted 3mo ago[deleted]
- small_model 3mo agoAgree, not only code but the plethora of tools usually required in a dev job, Jira, git, GitHub, build agents etc. These can all be accessed by the agent via API/MCP so you can say to the agent, describe my next ticket, create a branch off latest master and investigate the code re the ticket, later, codex/claude review the code (from other model), move the ticket to blah, add a comment, check the build (oh it failed dig into the logs), find any code review issues etc. All from a terminal, this used to be annoying clicking through web pages. I just eyeball the code and make sure it looks fine. Job done.