My first thought is, does this mean that along with the burnout I'm feeling with talking to my own agents I now need to try and consume and understand my teammates conversations with agents? Why is this better than a good pr description that distills completed work and explains why it was required ?
Yes, but compared to seeing 3k lines of code in a PR with no history with vibes in the description, what is better? This definitely "feels" like something worth exploring.
We never accepted 3k lines of code in a PR from a human, why do we from LLMs?
And if we're going to, why are LLMs not doing the PR review?
And if we don't trust them, then isn't that a rather large obstacle to the idea that LLMs are going to replace humans in software engineering?
You can defer review entirely to an LLM, only to human reviewers, or both. We are experimenting with both and have configured LLM skills for pull request reviews. On large projects we also configure LLMs to produce commit segregated diffs within a single pull request, to aid human review. This process is using the github pull request workflow that Zed is attempting to replace.
pipes · · focus · HN ↗
lnenad · · focus · HN ↗
SoftTalker · · focus · HN ↗
And if we're going to, why are LLMs not doing the PR review?
And if we don't trust them, then isn't that a rather large obstacle to the idea that LLMs are going to replace humans in software engineering?
waffletower · · focus · HN ↗