Technical Debt

Technical debt (also known as design debt[citation needed] or code debt) is a neologistic metaphor referring to the eventual consequences of poor software architecture and software development within a codebase. The debt can be thought of as work that needs to be done before a particular job can be considered complete. If the debt is not repaid, then it will keep on accumulating interest, making it hard to implement changes later on. Unaddressed technical debt increases software entropy.As a change is started on a codebase, there is often the need to make other coordinated changes at the same time in other parts of the codebase or documentation.
Posts about Technical Debt
  • Are You “Phoning In” Your Mobile Experience?

    …, cool and most importantly, contextually relevant. Moore's law hasn't overcome mobile technical debt Context is important because as advanced as modern internet and mobile technology has become, mobile is still in its infancy. Sure, we have the iPhone 6, wearables like glasses and watches, and our cars and airplanes have become WiFi hotspots to ensure…

    The IMPACT Blogin Google- 10 readers -
Get the top posts daily into your mailbox!