Have You Ever Reflected on Technical Debt?
In people's minds, technical debt looks like it accumulates because of some nasty, dirty practices but that is not the truth.
Join the DZone community and get the full member experience.Join For Free
Technical debt is widely used and discussed within engineering teams. However, in people's mind, it looks like it accumulates because of some nasty, dirty practices.
Technical debt piles up even when you work with the best engineers and follow the best practices.
Because Tech debt is not ONLY a result of prioritizing speedy delivery or poor development skills but also a natural result of writing code about something we don't have a proper understanding of the complete solution
Knowing that, a natural response is to invest more in the design phase. However, in reality, you can not capture and learn everything before start implementing the solution. The future is uncertain and might bring radical changes.
A leaner cycle is the best option. Take a piece of the Design effort and move it forward in a refactoring phase that happens every time a few pieces have consolidated and are ready to be secured.
In this scenario, we accept debt creation, trusting our ability to repay it in the short term.
Rush — the code out of the door
Learn — more things about your business reality
Refactor — put that learning back into the software
Like financial debt, tech debt can harm or help your organization. To use it wisely, engineers and team leaders must monitor how much technical debt they acquire and learn to manage it well.
Published at DZone with permission of Alexsandro Souza. See the original article here.
Opinions expressed by DZone contributors are their own.