← 返回起始笔记位置

知识卡片

普通读书笔记卡 · 1932.a.1

快速可靠构建保护修改意愿

理解等级:中级

一条命令应能从检出构建出开发者负责的部分,关键单元测试要快速且可信。验证太慢或覆盖不可靠,会让每次小改都背负大量人工确认,最终开发者不愿碰代码。团队应投资机器资源、测试基础设施与快速反馈;书中构建分钟数是经验目标,重点是验证成本不能阻止系统演进。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 构建与演进系统 · 查看原书依据

      Builds with unit tests should run in less than 15–20 minutes and should give the developers confidence that everything is good. If the build takes longer or unit tests do not cover key aspects, your developers will be reluctant to touch the code unless it is absolutely necessary.

    参考来源

    - 位置:《Software Architecture and Decision-Making》第13章《Building and Evolving the Systems》(来源项目:book-sources;源文件:extracted/Software Architecture and Decision-Making Leveraging Leadership, Technology, and Product Management to Build Great Products… (Srinath Perera)/_epub-src/ch13.xhtml) - 结论依据:摘录说明一条命令应能从检出构建出开发者负责的部分,关键单元测试要快速且可信。其余条件结合本章相邻例子与取舍说明,数字示例不作当前性能承诺。 - 原始内容:Builds with unit tests should run in less than 15–20 minutes and should give the developers confidence that everything is good. If the build takes longer or unit tests do not cover key aspects, your developers will be reluctant to touch the code unless it is absolutely necessary.