Code Room
Vibe codingMediumvc-g476
Subject Ai verificationLevel Mid–Senior~18 minCommon in Algorithms & data structures interviewsIndustries Software development

Question

A user reported that uploading a file over 5 MB sometimes fails with a 500. You gave the stack trace to an AI agent and it returned a fix that wraps the upload handler in a try/catch and returns a friendly 413 instead. The error stopped appearing in your manual test. How do you decide whether this fix addresses the root cause or just hides the symptom — before you merge it?

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.

Describe your solution

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.