← 返回刚才阅读的位置

知识卡片

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

拆后仍需减少依赖

理解等级:高级

若拆出的决定必须继续同步、彼此等待,拆分收益可能消失。团队可通过移动职责、隐藏内部信息的接口或其他有据设计,减少不必要联系。目标是稳定必要契约并让其余选择各自流动;不能为了少咨询而隐瞒真实影响。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Tackling Architectural Variability · 查看原书依据

      The way to solve this issue is to decouple decision parts in exactly the same way we would in software. Loose coupling between subsystems—both technical and social—enables small decisions. This is Reinertsen’s Principle B15: “Working with small batches requires that we reduce the dependency between batches.” In traditional architectural approaches, architects are responsible for managing

    参考来源

    - 位置:《Facilitating Software Architecture》第13章《Tackling Architectural Variability》(来源项目 /Users/wangyi/claudecodeProject/bookBase/book-sources;源文件:extracted/Facilitating Software Architecture/_epub-src/OEBPS/ch13.html) - 结论依据:原文以B15说明reduce dependency between batches,赋予团队主动消耦的能力。 - 原始内容:The way to solve this issue is to decouple decision parts in exactly the same way we would in software. Loose coupling between subsystems—both technical and social—enables small decisions. This is Reinertsen’s Principle B15: “Working with small batches requires that we reduce the dependency between batches.” In traditional architectural approaches, architects are responsible for managing