知识卡片
小范围讨论公开传播设计
架构会议不必让所有人每次都参加。可由相关负责人组织小范围深入讨论,再记录理由、API语义和决定,尽可能公开书面传播,让其他开发者仍可理解方向和参与质疑。架构所有者承担升级争议、维护记录与沟通的责任;限制参会人数只有配合透明信息才不会形成决策黑箱。
[[架构定边界团队设计细节]]需要这种公开传播与争议升级路径,才能避免放权后信息隔绝。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 构建与演进系统 · 查看原书依据
My recommendation is to do smaller meetings but take detailed notes, which can be edited by the architectural owners and shared with all developers. Also, any architecture discussion that can be done through writing (e.g., chats, shared documents, emails, and so forth) should be done as publicly as possible so that all developers can see it and understand its direction.
参考来源
- 位置:《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)
- 结论依据:摘录说明架构会议不必让所有人每次都参加。其余条件结合本章相邻例子与取舍说明,数字示例不作当前性能承诺。
- 原始内容:My recommendation is to do smaller meetings but take detailed notes, which can be edited by the architectural owners and shared with all developers. Also, any architecture discussion that can be done through writing (e.g., chats, shared documents, emails, and so forth) should be done as publicly as possible so that all developers can see it and understand its direction.