Prove It: Module 3 Check
A post-test on debugging and error handling, plus what changed since the start of the module.
📈 Compare, Don’t Just Answer
One of these revisits the prediction you made at the start of the module. See what’s different now that you’ve actually caused and fixed two real errors.
1. Your app shows a big red error message you don't understand. What's the correct next step?
You proved this yourself: report what you did, what happened, and what you expected instead. That's the full method, no translation required.
2. What's the difference between a crash and a silent bug?
A crash announces itself. A silent bug doesn't — it's why testing carefully, not just glancing at the app, matters so much.
3. The AI gives a confident, technical-sounding explanation for a fix. What confirms it actually worked?
Fluent explanations can still be wrong. Testing the specific behavior again is the only real confirmation.
🎉 Celebrate, Revisited
Think back to how a wall of red error text felt before this module, versus how it felt when you triggered it on purpose last lesson. If it went from dread to mild curiosity — that’s the actual shift this module was built to produce. Errors were never a verdict on your ability. They were always just clues, waiting to be reported clearly.
⏭️ Up Next
So far you’ve been building for yourself. Module 4 asks a harder question: is it actually good — good enough that a stranger would understand it in five seconds?