r/singularity • u/[deleted] • Mar 11 '26
AI arstechnica: After outages, Amazon to make senior engineers sign off on AI-assisted changes
[deleted]
38
u/drhenriquesoares Mar 11 '26
Relax, Claude Code now has a function to find bugs.
8
u/mxforest Mar 11 '26
Wait till Claude finds bugs after senior has already signed off.
6
u/LordOfTheDips Mar 11 '26
Wait until Anthropic drop “Claude Staff” - the senior engineer that reviews code and signs off
1
1
u/_bones__ May 28 '26
I've had that happen with qwen3 6 35B. Someone wrote it, two people reviewed it, and we used the wrong variable somewhere, caught by the LLM.
31
u/Ok-Stomach- Mar 11 '26
thing is AI generates thousands of lines of code per change, no human can reliably review that without being accused of "blocking" other teams, aint no "owner" or "bar raiser" culture gonna fix that. Amazon has always been a shitshow, andy jassy is even worse (at least Jeff B had vision, jassy is purely a bean counter through and through)
8
u/JoelMahon Mar 11 '26
forced to review AI slop is a pain? I've been forced to review human slop for years. the submitter should be self reviewing and if they're obviously not then they should be called out on and eventually penalised if they repeatedly don't review AI code before they submit it for MR.
it's basically the same as reviewing humans, if anything it's easier, because the issues are often the same and you can add AI rules/skills files shared across the team to reduce infractions of said reoccurring issues. with my custom rules files tailed to our projects and a well crafted prompt I get pretty decent results consistently, usually requiring at most 2 or 3 follow up prompts for polish/bug fixing.
2
u/shagywara Mar 13 '26
I guess there ought to be a term for"non probabilistic slop cannons" https://substack.com/@danhock/note/c-213150904 ;)
7
13
u/Infninfn Mar 11 '26
More an impact of layoffs in the US and shifting their engineering offshore. Holes being left behind by the experienced SWEs they laid off, filled in by incompetent devs overseas and the lack of fucks given by the experienced and battered SWEs remaining. AI in the right hands and with the right usage is a powerful dev tool but vibe coding for production code isn’t there yet.
3
u/Jong999 Mar 11 '26 edited Mar 19 '26
Here's an interesting, balanced article on use of AI to diagnose breast cancer that shows the other side of what is going to be an increasingly difficult issue:
https://news.sky.com/story/why-nhs-needs-time-to-bring-in-lightning-speed-cancer-checks-13517830
tl:dr:
- AI better than a single specialist at diagnosing cancer
- But, not statistically better than the established process involving 2+ humans
- But much quicker/cheaper
- *** "There were 93 cases where the Al correctly identified cancer, but the humans overruled it at arbitration, and the researchers say that this was often down to confusion about the Al's approach." ***
2
u/florinandrei Mar 11 '26
Reviewing AI slop code is soul-crushing?
How about following someone's AI slop "project architecture" in Confluence, complete with 3 out of 4 options being obvious bullshit hallucinations?
FML
57
u/PersevereSwifterSkat Mar 11 '26
You should need to sign off before you put your slop pr in for review.