Your goal: read unfamiliar code and extend it safely, then find the cause of a production
bug by asking for the right evidence in the right order.
How this works (about 30 minutes)
- Part one: a small service in the shared editor. Read it first, say your plan, then extend it.
Public tests run from the editor. Tell Ryan when you want him to look at your code.
- Part two: a bug report from production. Ryan holds the facts, the trace and the logs and gives
them only when you ask. Ask him to show the trace and he puts it on the notepad.
- A curveball about shipping the fix.
- No hints and no scores during the call. Your report comes after.
What scores well
- Reading the existing code before changing it, and saying what you see
- Small steps and a test early
- Reproduce, narrow, then fix: facts before guesses
- Two or three hypotheses, each with the evidence that would rule it in or out
- A fix and a guard, so the bug cannot quietly return
Tips
- Take FDE Coach · Extend and Debug first.
- Say what you would look at first, and why, before you look.