Question
An agent wrote the client-side prediction-and-reconciliation code for a multiplayer game in C#. It feels smooth in your single-machine playtest and the diff looks coherent, but you didn't write it and netcode bugs (desync, jitter, mispredicted rollback) only appear under real latency and packet loss. How do you verify this before it ships to players?
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.