How many times have you heard or uttered those words? You work hard and understand the business requirements, you try and get the logic to work to make the procedure return what was expected or update the data as expected. You do some unit tests in your environment, it may not scream but it comes [...]
When I posted about Empirical Evidence and finding a Troubleshooting Methodology, I talked about implementing a solution just because it seemed to work. This can manifest itself in different ways. Some are alright and harmless (what your shotgun hit happened to be the right fix) and some can be dangerous and hide the real problem.
Or how I learned to stop asking so much and start trying…
Empirical, as defined by Webster: 1.) originating in or based on observation or experience 2.) relying on experience or observation alone often without due regard for system and theory 3.)capable of being verified or disproved by observation or experiment.
I think empirical thought and evidence [...]
What is a troubleshooting methodology?
A lot of the technical problems I encounter with clients or in various roles are not really the fault of the technology at hand. They are either the result of rushed work, apathetic work or botched troubleshooting.
Before talking about what troubleshooting is, let’s talk about what it is not. It is [...]