Read Time : 3 mins
Intro
Ward Cunningham simple explanation to attribute tech debt is the consequences of poor choice in decision making while designing software and developing them. The preference to implement features and functions to deliver business value by the management results in counter-productive as it delays the team to focus on localised technical debt. This makes systems more vulnerable, slow and risky.
Uncovering the Foggy Side of Software development
Understanding the tradeoff between designing a clean code and risk if not done properly is key. The engineering teams are borrowing efficiency now in exchange for having to do more work mending the code later.
The dark matter effect
By now you would have fair understanding that technical debt impacts developers/ engineers, team and organizational level. Below are few to list
Addressing the Tech Debt
Understand the value of an application and prioritise those which are critical for business growth. Once the value of an application has been identified, leverage the above classification framework to prioritise addressing the debts
Conclusion
We build systems to support business to support operation and growth. It is very keen to understand weakness and finding a way to address them.
Further reading:
Top comments (1)
All to common, tech debt can so easily get out of hand, with a negative feedback loop of: