Sample page 3, from chapter 12
The first five minutes, before you type
Chapter 12 · Live coding
The method
Read the prompt back in your own words. It confirms you understood and buys a moment to think. Clarify only what changes your design. Two or three questions whose answers fork the build. Then name the risk out loud: "The interesting part here is the search, because typing quickly will race, so I want to handle cancellation. I will come back to that on purpose."
Why it works
Now the interviewer knows what to watch for, and you are the one who pointed it out. All of it fits in under five minutes, and by your first real line of code the interviewer has already seen how you think.
Common pitfall
The most common opening mistake is laying out a beautiful cell before there is any data flow, which burns the clock on the easy part and leaves the state and the async for the panicked final minutes.
