Stage 6 · Lesson 3 of 7
A routine for getting unstuck
works best as a routine, not as random code changes. First, restate the problem in one sentence. Make it happen again reliably.
Read the whole error message and the , the list of function calls that led to the error. Shrink the case until it is as small as possible. Check the logs, recent changes in the history and similar code elsewhere in the .
Search the team's docs and chat. If you are still stuck after your timebox, ask, and include everything you found. A method keeps you moving, teaches you the system and gives you a much better question if you do need help.
Common traptrying random changes until the error disappears, which leaves you unsure why it works and likely to break it again.
A question to check yourself, an AI practice session and 1 cheat sheet entry come when you add the roadmap to your account. Add it
Resources for this stage
Start with· follow one of these
- BookFreeSoftware Engineering at Google
Titus Winters, Tom Manshreck and Hyrum Wright · Intermediate
Free online: the chapters on knowledge sharing and testing show how strong teams learn and work
- BookPaidThe Pragmatic Programmer
Hunt and Thomas · Intermediate · About $45
Habits for learning, debugging and owning your work that last a whole career
Practise
Keep handy
Also worth your time
Why learning the systems under your daily work pays off faster than chasing new tools