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
About the Author
- New course: Career and Survival Strategies for Software Developers
- Simple Strategies to Eliminate Network Congestion Headaches!
- Troubleshooting IIS 7: Examining Trace Failed Request Logs
- New Training Release: VMware vSphere PowerCLI Training
- Cisco Network Troubleshooting for Beginners
- VMware VCAP-DCA Exam Section 6: vSphere Troubleshooting
- Windows 7 Troubleshooting Tips for IT Pros
- New course: Learning How to Program with Scratch
- New Course: SQL Server: Troubleshooting Query Plan Quality Issues
- Windows 7: Basic Home Network Troubleshooting