Understanding and Addressing Technical Debt
(This is an intro, the complete article will follow shortly after the weekend)
In software development, technical debt is?the implied cost of future reworking... when an implementation prioritizes quickness or convenience of implementation, while compromising quality.
Similarly to monetary debt, technical debt is not necessarily a bad thing, and sometimes (e.g. as a proof-of-concept) is required to move projects forward.
So... what's the problem?
But the interest we pay may be grossly underestimated, and implications a lot larger than we expect.
At some point, a project may not be able to find solutions when it comes across any issues, because of the past accumulated debt.
Like monetary debt, if not repaid, it can accumulate interest, making it harder to implement changes.
Can it be avoided?
There are some measures one can take to avoid it. We will look more into them soon in the upcoming continuation & conclusion (and beginning to a lot more possibilities to better quality) to this article.
"As an evolving program is continually changed, its complexity, reflecting deteriorating structure, increases unless work is done to maintain or reduce it."
(references: wiki, internet images)
Engineering Software with care
1 个月Added the concluding (though only the beginning...) article How do we deal with technical debt?! https://www.dhirubhai.net/pulse/how-do-we-deal-technical-debt-sanjay-mysoremutt-usnkc?utm_source=share&utm_medium=member_android&utm_campaign=share_via
Influential Engineering Leader Cloud-SRE-DevOps at Epsilon Publicis | Passionate Speaker | Opinions expressed are solely my own not the opinions of my employer | Working Hybrid | Alumini Oracle, PeopleSoft, Hexaware, HP
2 个月We also see tech debt bucketing of real bugs in any case error budgets should be used to account for them
Your CTO on hire | Product Managers' Tech-comrade-in-arms | Hands-on Server-side Rust, Java, Scala programmer |
2 个月I am happy to hear that you are taking up this topic for elaboration; one more time after the hundred of thousandth time (perhaps), it has been taken up in the past. I myself, have done. However, I appreciate your effort because the topic needs repetition. My realization has been that finally, it all depends on the stakeholders: who has / have real interest in seeing the software, being useful and successful (and therefore, are putting money). It is they who have to sit up and grasp that fact that known defects are a burden on the users and developers, and in turn, on the money bank. A significant number of regular business software , if not the significant majority of them, falls in this category. After all, most of them are, in their core, CRUD applications, aren't they? Then, what's the big deal really? I will wait for your upcoming installments and comment, if I think my comments will add any value to the discussion.
Progress not perfection!
2 个月If software is an engineering field and technical debt is allowed then it should be allowed in other fields of engineering too or software shouldn't be categorised in the field of engineering because of the bugs allowed. Imagine having the amount of bugs software has on a bridge or a road. It would be considered unusable. The majority of people working for software companies only fix any bug that pops up and they have no idea why it popped up. Im not saying this to insult the software field but to ensure that software should either have a limit to the the number of bugs like a bridge or a road or a car or any other field of engineering where there is a loss to life in the event of an issue and the Architects are issued legal notices. It is also to be noted that software does not take lives yet but it does bring the professional life to a stand still with just one update. That's how weak the system is. If the software community were to accept this and indicate that this is not a field of engineering since we cannot maintain the same level of quality like other engineering fields it would be a good place to start. If you would like this to change I would love to be a part of it. #myexperience and #myexplorations.