01/08/2026
Final transmission… 🚀 Are you ready for the finale?
Welcome to Level 3: Runtime Errors — when the code just stops, and you’re left staring at the screen to ACE your debugging skills! 👾💻
You’ve made it through every challenge so far. You caught syntax errors, fixed logic flaws, and pushed your problem-finding habits further each day. But now, you’ve hit the final test… the one that doesn’t warn you, doesn’t bargain, and doesn’t really give second chances. It just runs… and then everything sort of collapses. ⚠️🔥
Ever heard of the Ariane 5 Flight 501 failure? Read more below on how a $500 million rocket self-destructed in a span of 37 seconds after its liftoff. That’s the danger of runtime errors: they don’t show up until it's too late.
That’s why this level feels a bit different. This is where systems fail while they’re still running, and not after the fact. This is where assumptions crack in real time.
The Challenge:
We’ve intercepted a Python program that looks steady—until it stumbles over a value it wasn’t built to manage. Right at that moment, the program crashes. Your task is to track down the failure, pinpoint exactly what triggers it, and determine why it occurs during ex*****on. More than that, connect it to the real-world situation it represents. 🔎
This is the last challenge. The final level. The ultimate test of how you think like a debugger. ⚙️
Caption by: Jerome Cruz
Pub by: Fia Lansangan
As Per CSO-PNP Approved: OPA-08788
