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.
第二象限（慎重、故意）是最常见的技术债务表现。
Many am teams will see these decisions as premature and imposing an unwarranted technical debt.
许多的AM团队任务这些决定的是不成熟的甚至是毫无根据的。
We have simply incurred more technical debt than we would like and now is a good time to pay it down.
只是我们欠下了足够多的技术债，再也无法忍受，而现在是还债的好时候。
Technical debt: This refers to the work, which could not be done within the planned Sprint or Iteration.
技术死角：这指的是不能在计划Sprint或迭代中完成的工作。
Martin Fowler has written about four quadrants of technical debt (see Resources), as illustrated in Figure 1.
MartinFowler已经编写了技术债务的4个象限(见参考资料)，如图1所示。
There is nothing inherently bad about technical debt, just as there is nothing inherently bad in real-world debt.
技术债务并不是永远都是坏的，正如显示债务并不是永远都是坏的一样。
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.
在决定偿还债务之前，决策者对业务和技术风险都需要有深刻的理解。
The problem: the code bases of your projects are accumulating technical debt and they have already started to slowdown.
你的问题是：项目的基础代码一直在积累技术债务，但是这些债务已经开始下降了。
Technical debt resembles credit card debt: you don't have enough funds at the moment, so you borrow against the future.
技术债务类似于信用卡债务：您目前没有足够的资金，可以预支未来。
Next, I'll show two illustrations of technical debt: the first generated by hand and the second using a tool called Sonar.
接着，我将向您展示技术债务的两个插图：第一个是手工生成的，第二个是使用Sonar工具生成的。
However, if you have technical debt already, you must work around those compromised parts of the system to add new features.
但是，如果您已经拥有技术债务，则必须解决系统中那些折衷部分才能添加新功能。
This installment discusses how to estimate for emergent design, and how to make a convincing case for repaying technical debt.
这一期将讨论如何评估紧急设计，以及如何制定一个令人信服的偿还技术债务方案。
Three common patterns that I see driving exceptions are technical debt, overstuffing the pipe, and misaligned reward structures.
我发现有三种比较常见的模式，容易让人受不了——技术债、填的太满的管道、有问题的奖励制度。
You always have too much technical debt, too many problems, staff members quitting, not enough capital, customer complaints, etc.
初创企业总是有太多技术性债务，太多问题，员工辞职，资本金不足，客户抱怨等等。
Future — we have more features coming and hands-on experience with this code says that the technical debt will only slow us down.
未来——更多的特性在等着我们，已有的开发经验告诉我们现在的技术债会拖慢前进的步伐。
But there is more to your system than just code and documentation, and these other elements can incur technical debt just as well.
您的系统还有比代码和文档更重要的问题，而且其它这些部分也会造成技术债务。
Technical Debt is like a credit card that charges a high interest rate, just leaving the team with an outstanding balance cost.
技术债务就像信用卡一样，会有很高的利息率，就如同给团队留下了大量的帐务开销。
This is critical to keeping the technical debt under control and producing high-quality software that is potentially deployable.
对于让技术一直处于控制之中，并产生潜在可部署的高质量软件，这一点非常关键。
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.
在这种状况下，团队会很容易欠下一些很严重的技术债务，甚至有可能大大影响系统的质量。
This would depend a lot on the technical debt in the system but is a perfect way to ensure that the software which is being delivered is of the right quality.
这将很大程度上依赖于系统的技术负债，但这却是确保即将发布软件有质量保证的最佳途径。
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.
每个案例中，虽然几乎被技术债务压倒，但我们总不得不找到某些方法来减少债务——同时继续开发新的特性，不断前进。
应用推荐