Question
An agent wrote a cache-invalidation layer in Go for a high-traffic service. The logic is correct in every test you can think of, but cache-coherency bugs are notoriously the ones tests miss — they show up only under real concurrent traffic with real key distributions. You can't fully trust the code and you can't reproduce production locally. How do you verify it before and during rollout, beyond unit tests?
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.