Code Room
Vibe codingHard
Question
Deep into a long agent session building a Rust networking module, the agent fixes one borrow-checker error and reintroduces a different one it fixed an hour ago, then starts churning — each edit fixes one thing and breaks another. The context window is full of prior attempts. Why is it failing now, and how do you re-steer versus reset?
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.
Learn the concepts
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.
Run or narrate your approach, then ask the coach.