New Delhi: A flawed cybersecurity upgrade that crashed Windows systems caused a significant tech disruption that affected hospitals and airports last summer. This episode brings to light the crucial but frequently disregarded topic of technical debt in software, which is something that Professor Paris Avgeriou of the University of Groningen tackles in his studies and partnerships with businesses. Avgeriou stressed in her remarks during Cybersecurity Awareness Month how these hidden software issues might have serious repercussions if ignored.
Under pressure to meet deadlines, software engineers often turn to “duct tape solutions,” or quick fixes. According to Avgeriou, this is analogous to the manufacturing of automobiles: if two engine components are incompatible, they should be redesigned. But in software development, engineers frequently implement short-term fixes to keep things functioning with the intention of fixing them later—a process that is sometimes overlooked. Tight deadlines frequently force people to forgo high-quality software in favour of speed.
For instance, if Windows had a built-in system to identify errors in its core kernel, the update that caused airport shutdowns could have been readily fixed. However, implementing such a system necessitates re-examining judgements made decades ago, which is an expensive and difficult procedure.
Comprehending Technical Debt
The hidden expenses of these less-than-ideal solutions are referred to as technical debt. Using rapid patches makes it more difficult to make changes later on, which raises the debt’s “interest” rate. Although technical debt is invisible to end users, it’s becoming an issue for CEOs and CTOs. These days, it is more difficult to handle these issues without a large investment due to large, complicated software systems.
Avgeriou is a major contributor to global technical debt studies. His team works with businesses to identify the locations of these expensive solutions, calculate repair prices, and rank the issues according to the amount of debt that has to be fixed first.
Instruments for Technical Debt Identification
Tools like Arcan, created by Avgeriou’s research team, may detect technical debt in software architecture, which is the most costly kind to address. Arcan encourages managers to take action by assisting businesses in comprehending the financial ramifications of unpaid technical debt.
Avgeriou works with high-tech industries to assist businesses in resolving these problems before they result in expensive closures. Given how sophisticated software is becoming, his job is essential. As long as it doesn’t continue to expand, he explains, “sometimes you can leave some duct tape.”
