Notebook habits that survive the ABAP debugger week

Debugger week is not about typing speed. It is about leaving breadcrumbs that your future self recognizes during a client call. We ask for one page per include, with three bullets: intent, watch variables, and exit criteria.

When participants skip that discipline, they chase ghosts across duplicate function groups. The habit feels administrative until it saves an hour on the first group exercise debrief.

We also encourage screenshots only when the UI state cannot be described in one sentence. Slides full of identical screens rarely help during open-book reviews.

Finally, pair rotation is mandatory for two labs so vocabulary aligns between functional and technical teammates. The awkward pauses are part of the design.