Troubleshooting Strategies PosterBy Geoffrey Grosenbach
Troubleshooting is a skill that transcends programming languages, frameworks, and even time.
My first few years of professional programming were full of frustration. I would frequently run into problems and have no clue about how to solve them. I treated them as unexpected and unwanted interruptions.
Now I know that encountering and fixing problems is part of the developer’s job description. It’s a rare day that ends without unexpected behavior from code, a deployment, or another library.
But with the right plan, these unexpected events can be resolved quickly. Here’s the order of events we use regularly at Pluralsight:
- Gather data
- Isolate the fault
- Form a hypothesis
- Read the documentation
- Describe the problem
- Read the code
- Try another angle