4 Steps for Handling High-Pressure Bugs
I wrote about the strategy I use when dealing with high-pressure bugs in code.
When was the last time you heard that little voice in your head suggesting something might be amiss in your web app? 🤔 You know that nauseous feeling that forms in the pit of your stomach, when you realize something bad has or is happening?
The X-Factor: Or, How To Debug
Have you ever been around a person, or maybe you are that individual, who has the innate ability to figure out what’s wrong with _____? Merely glancing at the computer that is behaving strangely causes the problem to disappear, touching the printer results in printed pages, or opening the hood of the car stops the squealing?
It’s a strange phenomenon, but certain people possess the ability to diagnose a situation, survey the playing field, and effectively implement a solution. I’m sure you’ve seen it happen before.
Truth be told, I don’t believe these people have any special magic. It is far more likely they’ve spent time honing their ability to observe what’s going on, consider possible courses of action, and choose the one that has the best probability of fixing the problem.
This is called troubleshooting.