13/12/2022
"Technical debt is a concept in software development that refers to the extra development work that arises when code that is easy to implement in the short term is applied as opposed to implementing the best overall solution. This can make it harder to make changes to the code in the future, and it can also make the code more difficult to understand.
"This can result in many headaches: developers may have to spend more time and effort working on the code which can slow down development and increase the overall cost of the project. It might also take longer for new team members to understand the code and all its quirks.
"The problem is if we don’t keep track of these changes, even if we document our code properly, things can quickly get out of control. When other developers in your team, especially new members, go through the code, they’ll only learn about some of those implementations once they see a comment, and maybe use git blame to see which commit added the change.
"A way of solving this is keeping a TECHNICALDEBT.md file in your repository".
Read "Why you should have a TECHNICALDEBT.md in your repo" by our very own Maciej Baron here:
goodpraxis.link/BES
If you’re a developer with at least a couple of years of experience, you must have encountered technical debt. Here’s how to deal with it.