Should we just skip code review now?
ClaudiuDasca
19 points
5 comments
April 28, 2026
Related Discussions
Found 5 related stories in 95.9ms across 8,303 title embeddings via pgvector HNSW
- How to Kill the Code Review tonkkatonka · 14 pts · March 03, 2026 · 59% similar
- Ask HN: Hiring in the age of AI-assisted coding: what works? nitramm · 17 pts · April 10, 2026 · 59% similar
- Linus Torvalds on AI code review: Anybody who thinks all AI is slop is in denial victordw · 14 pts · April 22, 2026 · 58% similar
- Google Engineers Launch "Sashiko" for Agentic AI Code Review of the Linux Kernel speckx · 93 pts · March 18, 2026 · 54% similar
- Going full AI engineer, not touching code anymore maxheyer · 53 pts · May 19, 2026 · 54% similar
Discussion Highlights (4 comments)
ares623
I would actually love to see this happen. Mostly for the potential schadenfreude.
cyanydeez
no mention of scaffolding, upversioning old code, porting to new languages, refactoring. Alot of the things we talk about wanting to do are now greased. a Still requires the engineering, but there seems , escaping the token mill leaves a powerful.
i_love_retros
My team are just vibe coding now and code review is non existent. Just hit approve. Why should anyone waste their time and brain cells reviewing a massive pile of slop. If management want us to go all in on AI then we will. Full trust in its output. I'm genuinely looking forward to the first major corporate disaster to happen because no one really pays attention to what code changes are being committed. When everything starts collapsing sell popcorn?
memoryleakgame
With spec driven development We are largely now doing proof of functionality and a skim read and making sure it runs locally and deployed to a lower environment All in all its still time consuming and we have discussed moving to a dark factory but there is still immense value in at least knowing what each file is for and maintaining good isolation of code