知识卡片
履历驱动偏离问题
因为新工具有趣或能丰富简历而先选架构,会让问题被迫适应技术。先理解领域、必要特征和约束,再比较候选方案的收益及代价。技术学习可以另作实验目标,但不应暗中成为业务架构的主要驱动。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
- · 履历驱动偏离问题
原书出处 · 1 处
- Evolutionary Architecture Pitfalls and Antipatterns · 查看原书依据
Always understand the problem domain before choosing an architecture rather than the other way around. Incremental Change Many factors in software development make incremental change difficult. For many decades, software wasn’t written with the goal of agility in mind but rather around goals like cost reduction, shared resources, and other external constraints. Consequently, many organizations don’t have the building blocks in place to support evolutionary
参考来源
- 位置:《Building Evolutionary Architectures Automated Software Governance, 2nd Edition》第08章《Evolutionary Architecture Pitfalls and Antipatterns》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Evolutionary Architectures Automated Software Governance, 2nd Edition/_epub-src/OEBPS/ch08.html;段落定位:Always understand the problem domain before choosing)
- 结论依据:原文对“履历驱动偏离问题”的定义或案例,支撑“因为新工具有趣或能丰富简历而先选架构,会让问题被迫适应技术”的归纳。据其上下文,先理解领域、必要特征和约束,再比较候选方案的收益及代价。
- 原始内容:Always understand the problem domain before choosing an architecture rather than the other way around. Incremental Change Many factors in software development make incremental change difficult. For many decades, software wasn’t written with the goal of agility in mind but rather around goals like cost reduction, shared resources, and other external constraints. Consequently, many organizations don’t have the building blocks in place to support evolutionary