Worker pool race condition
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:
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?
Implement
schedule_pool_results(job_ids: list[str], durations: list[int], workers: int) → list[str]Examples
in
[["a","b","c"],[3,1,2],2]out["a|3","b|1","c|3"]in
[["j2","j1"],[5,5],1]out["j1|10","j2|5"]in
[["a","a","b"],[2,7,1],3]out["a|2","b|1"]What a strong answer looks like
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.
0:00 of about 22 min
Vibe & agentic: describe the solution in plain language (or narrate it) and the coach grades your approach.
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.