▲ 381 ▼ AI coders think they’re 20% faster — but they’re actually 19% slower (pivot-to-ai.com) submitted 1 year ago by dgerard@awful.systems to c/techtakes@awful.systems 102 comments fedilink hide all child comments podcast version video version
[+] Feyd@programming.dev 19 points 1 year ago (1 child) [deleted] permalink fedilink source parent hideshow 1 child comment replies: [–] diz@awful.systems 7 points 1 year ago* (last edited 1 year ago) I think more low tier output would be a disaster. Even pre AI I had to deal with a project where they shoved testing and compliance at juniors for a long time. What a fucking mess it was. I had to go through every commit mentioning Coverity because they had a junior fixing coverity flagged "issues". I spent at least 2 days debugging a memory corruption crash caused by such "fix", and then I had to spend who knows how long reviewing every such "fix". And don't get me started on tests. 200+ tests, of them none caught several regressions in handling of parameters that are shown early in the frigging how-to. Not some obscure corner case, the stuff you immediately run into if you just follow the documentation. With AI all the numbers would be much larger - more commits "fixing coverity issues" (and worse yet fixing "issues" that LLM sees in code), more so called "tests" that don't actually flag any real regressions, etc. permalink fedilink source parent
[–] diz@awful.systems 7 points 1 year ago* (last edited 1 year ago) I think more low tier output would be a disaster. Even pre AI I had to deal with a project where they shoved testing and compliance at juniors for a long time. What a fucking mess it was. I had to go through every commit mentioning Coverity because they had a junior fixing coverity flagged "issues". I spent at least 2 days debugging a memory corruption crash caused by such "fix", and then I had to spend who knows how long reviewing every such "fix". And don't get me started on tests. 200+ tests, of them none caught several regressions in handling of parameters that are shown early in the frigging how-to. Not some obscure corner case, the stuff you immediately run into if you just follow the documentation. With AI all the numbers would be much larger - more commits "fixing coverity issues" (and worse yet fixing "issues" that LLM sees in code), more so called "tests" that don't actually flag any real regressions, etc. permalink fedilink source parent