When do you throw versus return error codes?
PICTURE THIS: RAG CHATBOT
Simple meaning
Exceptions for rare failures that unwind cleanly
WHY — Errors instead of guessing?
Why interviewers care about Errors:
contrast on Errors, not two memorised paragraphs.
the developer, then one case where picking wrong hurts.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1Exceptions for rare failures
that unwind cleanly
- 2error codes or expected
for common failures in tight APIs.
- 3How it works
Consistency beats ideology.
- 4Give an example
Destructors should not throw.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
Exceptions for rare failures that unwind cleanly error codes or expected for common failures in tight APIs.