Is Your HA/DR Solution a By-product of Technical Malpractice
Medical malpractice is the term used when a healthcare professional or organization did something that caused an injury to a patient.
Although we don't have anything we can consider as "patients" in the IT field, I wonder how it would be like if we unknowingly performed malpractice?
Our role as an IT professional is to provide technical guidance and solutions to business problems. It's the reason why we got hired in the first place.
But often, because we are too absorbed in the technical details of a specific solution, we immediately jump into problem-solving mode.
We recommend solutions because we assume we know exactly what the problems are...
We provide a step-by-step process on how to solve the problem to prove that we are smart...
We immediately jump into problem-solving mode because we feel that our value and self-worth comes from providing solutions...
I see this a lot in online communities like forums and newsgroups. A technical solution is almost always the default response to a technical problem.
But is this really the right way of doing things?
Is immediately providing a solution the best way to solve a technical problem?
The bottom line is, providing a technical solution to a business problem without a clear understanding of the real issues can be considered technical malpractice.
In this episode of the Practical SQL Server HA/DR Show, I'll talk about how to evaluate if your existing HA/DR solutions are by-products of technical malpractice.