In technical debt terms, this means you would tackle the smallest fixes first.
在技术债务方面，这就意味着首先处理那些工作量最小的任务。
Complexity arising from the compromises we make that incur technical debt is different.
由导致技术债务的折衷引发的复杂度是不同的。
The hard-to-read code that underlies technical debt also makes it more difficult to find bugs.
同时，这些难读的代码引起的技术债务也让我们难以找到软件的缺陷。
The second quadrant (prudent and deliberate) is the most common manifestation of technical debt.
第二象限（慎重、故意）是最常见的技术债务表现。
Martin Fowler has written about four quadrants of technical debt (see Resources), as illustrated in Figure 1.
MartinFowler已经编写了技术债务的4个象限(见参考资料)，如图1所示。
Unfortunately, many managers don't seem to understand technical debt, causing resistance to revisiting past work.
糟糕的是，许多经理人似乎都不理解技术债务，因而不愿意重新完成旧的工作。
I've never agreed with that notion, since I think there are times when you simply need to pay down technical debt.
我从来都不赞同这个说法，因为我觉得有的情况只需要偿还技术债。
The decision to pay down technical debt requires a solid understanding of both the business and technical impacts.
在决定偿还债务之前，决策者对业务和技术风险都需要有深刻的理解。
Next, I'll show two illustrations of technical debt: the first generated by hand and the second using a tool called Sonar.
接着，我将向您展示技术债务的两个插图：第一个是手工生成的，第二个是使用Sonar工具生成的。
This installment discusses how to estimate for emergent design, and how to make a convincing case for repaying technical debt.
这一期将讨论如何评估紧急设计，以及如何制定一个令人信服的偿还技术债务方案。
Future — we have more features coming and hands-on experience with this code says that the technical debt will only slow us down.
未来——更多的特性在等着我们，已有的开发经验告诉我们现在的技术债会拖慢前进的步伐。
Because so many projects face technical debt situations, let's take a look at each of these steps and see how they apply - and how they can help.
因为有那么多项目都面临着技术债务问题，就让我们检查这些步骤，看看它们是如何应用的——以及它们是怎么帮助我们的。
In this situation, the team incurs typically into some significant technical debt or, even worse, the external quality of the system is severely affected.
在这种状况下，团队会很容易欠下一些很严重的技术债务，甚至有可能大大影响系统的质量。
Maintain a technical debt Backlog - anytime a developer notices some technical debt that they can't address immediately, get them to write a technical debt card.
维护关于技术债务的备忘录—任何时候，如果开发人员发现一些无法立即应付的技术债务时，就需要填写一份技术债务登记卡。
You might want to put off new development in only that area while you repay any technical debt in that section (refactoring code, updating documentation, and so on).
您或许想要仅在那个范围内推迟新的开发，同时在该部分内偿还技术债务(进行代码重构，更新文档等等)。
Every developer becomes aware of the concept of technical debt, whereby you make compromises in your design for the sake of some external force, such as schedule pressure.
每位开发人员都开始注意到技术债务的概念，您可能由此而迫于外部压力(例如日程压力)在设计中有所折衷。
For each case, while nearly overwhelmed with technical debt, we had to find some way to reduce that debt — while still continuing to develop new features and move forward.
每个案例中，虽然几乎被技术债务压倒，但我们总不得不找到某些方法来减少债务——同时继续开发新的特性，不断前进。
However, I'd say it is generally a very good thing for business and technical folks to work closely together so that these kinds of technical debt decisions are Shared by everyone.
但是，我认为通常情况下，让业务人员和技术人员在一起紧密工作是非常好的事情。这样，大家都能共同做出关于技术债的决定。
"The system" represents the program itself, which would have a stake in backlog items representing program improvements such as technical debt items and the upgrading of any frameworks.
“系统”表示程序自身，它关注表示程序改进的待办事宜条目，比如技术债务相关的条目、任何框架的升级等等。
Technical debt resembles credit card debt: you don't have enough funds at the moment, so you borrow against the future.
技术债务类似于信用卡债务：您目前没有足够的资金，可以预支未来。
Technical debt resembles credit card debt: you don't have enough funds at the moment, so you borrow against the future.
技术债务类似于信用卡债务：您目前没有足够的资金，可以预支未来。
应用推荐