← 返回刚才阅读的位置

知识卡片

普通读书笔记卡 · 4918.b.2.a.1.a.1.a.2

原则不同于实践和CFR

理解等级:中级

TDD、配对编程等实践讲人怎样工作;CFR具体规定系统需要什么;架构原则则给出构造系统的常用方向,帮助比较方案。原则可因张力或特定情境有据偏离,不能把它假装成不容讨论的要求;同时也不应用宽泛原则替代明确可验收的硬条件。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Collectively Sourced Architectural Principles · 查看原书依据

      First, architectural principles are not practices. Principles describe how things in your architecture “happen or work.” Practices tell you how to make those things. Some examples of practices are TDD, trunk-based delivery, and pair programming. These practices are ones I advocate for myself, but they’re not architectural principles. If a principle doesn’t provide you with

    参考来源

    - 位置:《Facilitating Software Architecture》第10章《Collectively Sourced Architectural Principles》(来源项目 /Users/wangyi/claudecodeProject/bookBase/book-sources;源文件:extracted/Facilitating Software Architecture/_epub-src/OEBPS/ch10.html) - 结论依据:原文比较principles/practices,再以CFR是what且nonnegotiable、原则是how区分。 - 原始内容:First, architectural principles are not practices. Principles describe how things in your architecture “happen or work.” Practices tell you how to make those things. Some examples of practices are TDD, trunk-based delivery, and pair programming. These practices are ones I advocate for myself, but they’re not architectural principles. If a principle doesn’t provide you with