Agents fail like engineers, so I review them like engineers
Azkar
11 points
3 comments
October 23, 2026
Related Discussions
Found 5 related stories in 236.2ms across 10,409 title embeddings via pgvector HNSW
- I stopped reviewing my agents' code. Here's what I do instead alexeyindeev · 12 pts · October 04, 2026 · 63% similar
- AI Agents and the Refactoring That Never Happens rosenfeld · 42 pts · September 02, 2026 · 59% similar
- How well do agents use test/verification techniques? vinhnx · 43 pts · September 08, 2026 · 58% similar
- AI Coding Agent Skills for Real Engineers gurjeet · 21 pts · September 01, 2026 · 57% similar
- How to Build an AI Software Factory: Agents That Open, Review, and Merge PRs makaimc · 29 pts · September 11, 2026 · 56% similar
Discussion Highlights (2 comments)
spike021
I like how you break down each type by how the agent compares to human behavior. Granted I don't know the specifics behind training LLMs but at the end of the day they are typically trained on data that originated from humans. So in some ways it's better to try and understand their contributions to our work from that mindset than just saying they are computers/text generators.
shibboleth
With these multi-agent workflows, I often wonder when coordinating the agents and reviewing their findings starts taking more time and effort than working with a single agent. Do you have a good feel for when (if ever) that happens? Relatedly, I'm seeing more and more people who are opening and closing a hundred pull requests a day, and outside of areas like performance profiling, I have a hard time understanding how that is being achieved. Are you finding yourself naturally gravitating toward that type of velocity and having to push back on it? Or do you see these types of workflows eventually allowing you to achieve a similar pace of change while still maintaining an emphasis on human reviews?