知识卡片

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

相似不等于同一问题

理解等级:中级

同叫客户或配置的东西,可能承担不同业务职责。若只因同名或少量共同数据就捆成一个决定,会扩大范围并错误抽象。先检查不同用途、用户和变化原因,真正相同部分才会浮现。拆决定不要求最终代码一定不同组件,但避免过早把问题绑死。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Tackling Architectural Variability · 查看原书依据

      As you look for places to split, beware of a predisposition among both developers and architects to assume that if situations seem similar, then they must be the same. Over and over, I observe gigantic decisions not being split solely because of some small shared element. This predisposition arises, in my experience, from

    参考来源

    - 位置:《Facilitating Software Architecture》第13章《Tackling Architectural Variability》(来源项目 /Users/wangyi/claudecodeProject/bookBase/book-sources;源文件:extracted/Facilitating Software Architecture/_epub-src/OEBPS/ch13.html) - 结论依据:原文警告similar trap,并主张按difference与domain nuances寻找断裂面。 - 原始内容:As you look for places to split, beware of a predisposition among both developers and architects to assume that if situations seem similar, then they must be the same. Over and over, I observe gigantic decisions not being split solely because of some small shared element. This predisposition arises, in my experience, from