Question
An agent opened a 1,400-line PR in Go that migrates your in-process job runner to a worker pool. You cannot line-by-line review all of it, and a sample of the code looks clean. One file caught your eye:
func (p *Pool) Submit(job Job) { p.wg.Add(1) go func() { defer p.wg.Done() p.results[job.ID] = process(job) }()} func (p *Pool) Wait() map[string]Result { p.wg.Wait() return p.results}As the reviewer accountable for this merge, what's your strategy for a 1,400-line agent PR you can't fully read, and what specifically is wrong here that the 'looks clean' sample would hide?
Treat the AI’s output as a draft to verify, not an answer to trust. Name the specific flaw and the input that triggers it, say how you’d catch it — tests, edge cases, reading critically — and how you’d re-prompt or decompose to get it right.
Vibe coding: describe the solution in plain language (or narrate it) and the coach grades your approach. Generating runnable code from your description is coming next.