Question
A Go service throws intermittent 'connection reset by peer' errors under load. You paste the stack traces and a code snippet into an AI agent and it concludes with high confidence: "Root cause: you're not setting a read timeout on the HTTP client, so slow upstreams pile up connections — add client.Timeout = 30s and it's fixed." The fix is plausible and easy. Before you ship it, how do you verify this is actually the root cause and not a coincidence?
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.