06/11/2026
Too often in IT, the code changes before the problem is understood.
A process fails, a report produces the wrong figures or an application throws an error.
And before anyone has properly investigated what's going on, someone is already changing code.
But do we actually understand what's causing the problem?
Whatever happened to the art of troubleshooting?
Some of the most valuable lessons in IT come from experienced colleagues who take the time to teach others.
They don't necessarily give you the answer. They teach you how to find it.
How to investigate, follow the evidence, eliminate possibilities and understand why something isn't working before attempting to fix it.
Sometimes that means spending hours investigating something that turns out to have a very simple explanation.
But that's part of learning.
We do wonder whether we're losing some of that.
Under pressure to deliver, time for mentoring can easily disappear. Deadlines need meeting, projects need delivering and problems need fixing.
It's often quicker to give someone the answer or make the change yourself than spend time teaching them how to work it out.
But what are we creating in the process?
People who know how to write code, but haven't necessarily learnt how to troubleshoot it.
And there's a big difference.
Without understanding the cause, a change can hide the symptom, introduce another issue or leave the original problem waiting to happen again.
At DDS, we see troubleshooting as one of the most valuable skills in IT. It's not just about technical knowledge. It's about knowing how to think through a problem.
A course or certification can help build that skill. But it also develops through experience, making mistakes and working alongside people willing to share what they've learnt.
Making time for that is an investment in the team's ability to solve the next problem.
Are we so focused on fixing today's problems that we're forgetting to develop the people who need to solve tomorrow's?