Design debt actually has its place.
设计债实际上拥有它的位置。
Design debt and code maintainability.
设计债以及代码可维护性。
Third, the existing design debt must be reduced.
第三，已存在的设计债问题必须得到减少。
Why can't we just use 'new'?"), but it's all about design debt.
为什么我们不能直接用'new'去创建对象？”） ，但这一切都是要去偿还设计的债务。
Kerievsky USES the design debt analogy to communicate with managers.
Kerievsky使用设计债类比来与管理员进行交流。
As mentioned above, dealing with design debt requires a three-pronged approach.
如上所述，处理设计债需要三步的方法。
A metaphor though it is, the real bottom-line costs of design debt cannot be ignored.
虽然这只是一种比喻，但是设计债的实际底线成本也不能被忽略。
If the design debt issue is to be resolved, a three-pronged approach should be employed.
如果想要设计债问题得到解决，可以采用一个三步的方法。
So, when a team finds itself in great design debt, it may be time for some tough decisions.
所以，当一个团队发现它有大量的设计债时，那么是时间该作出一些决定了。
I routinely take out a credit card and show it to managers when I'm speaking about design debt.
我通常都是拿出一张信用卡，并在谈到设计债时向管理员展示它的。
Discussions like this help managers acknowledge the wisdom of continuously paying down design debt.
像这样的讨论可以帮助管理员们意识到，按时还清设计债的智慧所在。
In this article, I use a financial metaphor, design debt, to show the importance of code maintainability.
在本文中，我使用了一个金融比喻，设计债(Design Debt)，以显示代码维护性的极端重要性。
Once the issue of design debt is acknowledged, debt should be recorded whenever it is incurred or identified.
一旦设计债的问题得到了承认，那么过失就应该得到记录，不管它是担负的还是识别的。
Once design debt has been identified and logged, repayment via refactoring should certainly be made a priority.
一旦设计债得到识别和标记，通过重构进行偿付应该放在优先的位置。
Design debt can be set apart, by tagging it with a "design-debt" designation, or by using a distinct work item type.
设计债可以通过标记“设计债”，或者使用不同的工作项类型，来进行分开处理。
Discussing technical problems using the financial metaphor of design debt is a proven way to get through to management.
使用设计债的金融比喻的技术问题，被证明是管理的一种有效形式。
Since design debt is technical and not functional in nature, this activity may be considered "noisy" to non-developers.
因为设计债在本质上是技术性而不是功能性的，这些活动对于非开发员来说可以是非常“烦人的”。
There is not a development team in the world that doesn't deal with design debt (though it may be doing so unknowingly).
在世界上并不存在一个完全不与设计债打交道的开发团队(有时候它自己并没有意识到这一点)。
Design debt results when a development team is not skilled in, committed to, and discerning about code quality practices.
当开发团队对代码质量操作不在行，不负责或者不关注时，设计债问题就会产生。
The defect tracker chosen for tracking design debt should be fast and easy to use, and it should accommodate rapid capture.
追踪设计债所需的缺陷追踪器应该可以很快且很容易的使用，而且适应快速的获取。
This can be helpful if the customer and test organization does not wish to have constant visibility to design debt activity.
如果客户和测试机构不希望对设计债活动有稳定的可视性，这就可以变得十分有用了。
The sooner teams start managing design debt, the more likely it is that they can avoid paying interest that they'd rather not pay.
团队越快开始管理设计债，它们避免支付不喜欢付的利息的可能性就越大。
Next, so that the design debt withdrawals can stop, the development team must attain the ability to write more maintainable code.
接下来，因为设计债问题可以停止，所以开发团队必须获取书写更具维护性的代码的能力。
The bottom line is that in order to avoid them, design debt must be regarded and respected early enough that bankruptcy is not risked.
设置底线就是为了避免这一点，设计债必须尽可能早的意识到并得到尊重，这样就可以不受破产的风险了。
Due to ignorance or a commitment to "not fix what ain't broken," many programmers and teams spend little time paying down design debt.
由于无知或者对“只要还能用就不要去管它”原则的坚持，许多程序员和团队在设计债问题上花费了很少的时间。
When design debt is extreme, it is often faster and less risky to rewrite the debt-ridden body of code than to attempt to improve it.
当设计债十分严重时，重写代码的出问题部分，要比试着修复它更快，风险性更小。
If the tracker used is difficult to use, too rigorous, or it "pushes back," then design debt won't be captured whenever it is encountered.
如果使用的追踪器很难使用，太过严格，或者它“延后”，那么不管碰到它设计债都不会被获取。
Once management accepts the importance [of keeping design debt under control], the organization's entire way of building software can change.
一旦管理层接受了不断控制设计债这种理念，那么公司构建软件的所有方式都会发生改变。
When any team comes to realize that it has been incurring great design debt, the first thing they must do is get control over the withdrawals.
当任意的团队开始意识到，继续取款会招致更大的设计债，那么他们需要做的第一件事情，就是控制取款。
Author and software consultant Joshua Kerievsky helps explain the literal truth of design debt. This quote is in the context of compound interest.
作者和软件咨询员Joshua Kerievsky帮助解释了设计债的字面真意。
应用推荐