OSCON 2007:管理技术债务

tech2024-04-07  59

Andy Lester is with the Perl Foundation, and maintains a blog at petdance.com.

Andy Lester在Perl Foundation 任职 ,并在petdance.com上维护一个博客。

Andy’s talk gave practical advice for catching up on all the tasks you put off until some later date (that inevitably never comes) — stuff like postponed docs, fixing broken tests (or just writing tests at all), backup regimes, TODOs in your code, etc.

安迪(Andy)的演讲提供了实用的建议,以解决您推迟到某个日期(不可避免地永远不会出现)的所有任务-诸如推迟文档,修复损坏的测试(或根本只编写测试),备份机制,代码中的TODO之类的事情等

He had a very simple and straightforward formula:

他有一个非常简单明了的公式:

Identify your debts

识别您的债务 Determine the costs

确定成本 Pay the most profitable

支付最赚钱的 Stop incurring new debt

停止产生新的债务 Repeat as necessary

根据需要重复

The most important takeaway for me was the idea that you don’t try to fix all your problems at once. You figure out what fix will give you the most bang for your buck — not the easiest thing to fix, not the biggest problem. You fix whatever it’s the most profitable to fix.

对我来说,最重要的收获是您不尝试立即解决所有问题的想法。 您会弄清楚哪种修补程序将为您带来最大的收益—不是最容易解决的问题,也不是最大的问题。 您可以修复最有利可图的内容 。

There was also a lot of good discussion during this talk on how to convince a manager to allow you to begin reducing technical debt with things like refactoring, increasing test coverage, adding documentation, or actually testing your disaster-recovery plan. The best advice was the idea of putting it in terms that the manager can understand (often with a manager either in money or time).

在本次演讲中,关于如何说服经理人使您开始通过重构,增加测试范围,添加文档或实际测试灾难恢复计划等减少技术债务的问题,也进行了很多精彩的讨论。 最好的建议是将其表达为经理可以理解的术语(通常与经理在金钱或时间上)。

For example, if managers know that investing two days testing disaster recovery would save weeks of rebuilding critical infrastructure, or that spending a week refactoring crufty old code would make it 20% faster to implement new features, it’s easier for them to justify the cost.

例如,如果管理人员知道花两天时间测试灾难恢复可以节省数周的关键基础架构重建工作,或者花一周的时间重构旧的旧代码会使实施新功能的速度提高20%,那么他们就更容易证明成本合理。

Andy has his slides available online here.

安迪(Andy)的幻灯片在这里在线提供 。

翻译自: https://www.sitepoint.com/oscon-2007-managing-technical-debt/

相关资源:设计模式:Los 23 patrones dediseñoscon ejemplos-源码
最新回复(0)