Technical debt is a concept in programming that reflects the extra development work that arises when code that is easy to implement in the short run is used instead of applying the best overall solution. Technical debt is commonly associated with extreme programming, especially in the context of refactoring.
Technical debt is a phrase originally coined by software developer, Ward Cunningham, who in addition to being one of 17 authors of the Agile Manifesto, is also credited with inventing the wiki. He first used the metaphor to explain to non-technical stakeholders at WyCash …
Technical debt describes the consequence of implementing partial or quick software development solutions instead of time-consuming, yet more effective, long-term solutions. Managing technical debt well is a task that requires wisdom and balance on behalf of developers and organizations.
What Is Technical Debt? Where Does It Comes from?
Technical debt is the additional work needed to complete the software development. But this notion does not refer solely to the projects that are in development. This issue often follows the
Technical debt is often the elephant in the room that we choose to ignore, but we do so at our own peril. Technical debt is directly responsible for many of the problems we have in building high
Technical debt is no different. It allows companies to create software faster, with the understanding that they will slow down software development in the future. Companies will eventually be forced to spend more time fixing the debt than the amount of time it took them to …
Technical Debt is what makes code hard to work with. It is an invisible killer of software, and must be aggressively managed. In this post I define Technical Debt and describe some of the issues.
Just as smart financial debt can help you reach major life goals faster, not all technical debt is bad, and managing it well can yield tremendous benefits for your company.
Technical debt is inefficiency in a codebase that compounds over time (hey — just like credit card debt!). The inefficiency may be related to maintainability, performance, bugs, or style. As such, ignoring technical debt will hurt your team in the long term by making it take longer to get things done, making the product sluggish, having more
Preventing technical debt is what allows development to be agile in the long run. The main, or master, branch of the code base should always be ready to ship. That’s priority number one. So new features begin their lives on a task branch containing code for the feature itself, plus it’s automated tests.
Technical debt will always be there, no matter what. It will haunt you for the rest of your product manager career. It also affects if you can release your product on time or will always struggle while delivering over time/budget.