知识卡片

普通读书笔记卡 · 1741.b.2

工具适配必须实证验证

理解等级:高级

使用成熟工具可能节省交付与演进成本,但当前版本必须真正支持自己的用例,而非寄希望厂商将来补齐。把新工具当未知,查文档、问实际用户、做功能和性能验证;还要确保出问题时能调查并找到绕过办法,可通过内部专家或明确支持安排补齐能力。勉强适配通常会把复杂性转回架构。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 宏观架构导论 · 查看原书依据

      We need to always start by considering the tool as an unknown (principle 6 in Chapter 2). We should explore and verify that the tool can support the immediate use cases up to rewrite or print (question 4 in Chapter 2). Dig deep into the tool’s documentation and use cases and talk to developers and other users who are making use of the same tool. This verification needs to include performance.

    参考来源

    - 位置:《Software Architecture and Decision-Making》第5章《宏观架构导论》(来源项目:book-sources;源文件:extracted/Software Architecture and Decision-Making Leveraging Leadership, Technology, and Product Management to Build Great Products… (Srinath Perera)/_epub-src/ch05.xhtml) - 结论依据:原文的定义、比较或例子支持“使用成熟工具可能节省交付与演进成本,但当前版本必须真正支持自己的用例,而非寄希望厂商将来补齐”;正文据此说明用途和边界。 - 原始内容:We need to always start by considering the tool as an unknown (principle 6 in Chapter 2). We should explore and verify that the tool can support the immediate use cases up to rewrite or print (question 4 in Chapter 2). Dig deep into the tool’s documentation and use cases and talk to developers and other users who are making use of the same tool. This verification needs to include performance.