Theory Card 076 — Error Detection / Breakdown
Research lens
Error detection relies on having reference points that make mismatches visible. In the Breakdown stage of BASIC, the goal is to decompose the prompt into named parts. That makes this concept especially relevant here, because it shapes how much mental work the candidate is trying to carry at once and what gets made explicit.
Why it matters in SWE interviews
In coding rounds this means edge cases and invariants; in design rounds it means bottlenecks, outages, and abuse cases. Structure and Check create those reference points by naming what should happen before execution is complete. In practice, Breakdown is where the candidate should ask: What exactly is the problem asking, what are the constraints, and what is the shape of the input and output? That question acts like a cognitive boundary. It protects the answer from turning into an unstructured search.
BASIC move
A strong move here is to split the problem before trying to solve it. For Error Detection, that means deliberately naming the important units instead of juggling them implicitly. The interviewer sees cleaner reasoning, and the candidate benefits from prevents premature solutioning and keeps working memory from being flooded too early.
Common miss
The miss is discovering mistakes only after the interviewer asks a pointed follow-up. When that happens, the candidate usually feels busy, but the answer is actually becoming less inspectable.
Practice prompt
“While practicing, pause at the Breakdown step and explain how Error Detection changes the way you would handle the prompt.”