Why IT debt is mounting Network World IT debt poses challenges across the organization, but the pain point is most acute for CIOs charged with not only setting technical direction for the company, but who are also responsible for IT projects that...
A few weeks ago I went through my elaborate and entirely scientific calculation of the total technical debt in existence. But for all of those who fell asleep halfway through, a portion has now been re-imagined in the form of a handy infographic.
Recently I've been hearing people use the term technical debt to describe all sorts of things that are related to system improvement. However, used properly, technical debt is not a catch-all phrase for system improvement work, but a subset of that work. What is Technical Debt? Ward Cunningham first
Everything has an appointed season,and there is a time for every matter under the heaven.— Ecclesiastes, chapter 3The problem of analogiesIn software development, the dreadful consequences of (Pēdējā laika labākā lasāmviela no Maiz Lulkin puses
1. Types of Technical Debt An outline to use when discussing technical debt: Unintentional Intentional: (a) Short-term: Only if there is the commitment to schedule, prioritize, and fix soon (e.g., in the next sprint).
The problem: “just good enough” architecture is sloppy architecture. It’s inherently and intentionally short-sighted, which means that we’re avoiding any planning of architectural debt because we erroneously think that makes us “Agile.” But in reality, the planning part of “well-planned technical debt” is a part of your architecture that goes beyond “just good enough,” and leaving it out actually makes us less Agile.
Microsoft's layoffs have to make sense CITEworld More than anything, the old way created a technical debt problem. The longer we wrote code in isolation, the more debt we created. The bug curve grew and grew.