知识卡片

普通读书笔记卡 · 5406

小改动累积架构债

理解等级:中级

开发者为眼前功能与修复作局部决定,若不了解结构或受时间压力驱动,会逐渐侵蚀可修改性、性能和安全,形成架构债。重构不只清理重复代码,也可改变模块和子系统边界,如把反复共同变化的部分归并,恢复内聚。需用质量目标指导重构,避免把任何代码变化都称还债。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 理解质量属性 · 查看原书依据

      This “death by a thousand cuts” is common on software projects. Developers may make suboptimal decisions due to a lack of understanding of the structures of the system, schedule pressures, or perhaps a lack of clarity in the architecture from the start. This kind of deterioration is a form of technical debt, called architecture debt.

    参考来源

    - 位置:《Software Architecture in Practice, 4th Edition》第3章《理解质量属性》(来源项目:book-sources;源文件:extracted/Software Architecture in Practice, 4th Edition/_epub-src/ch03.html) - 结论依据:原文的定义、机制或比较支持“开发者为眼前功能与修复作局部决定,若不了解结构或受时间压力驱动,会逐渐侵蚀可修改性、性能和安全,形成架构债”;正文保留其条件与取舍。 - 原始内容:This “death by a thousand cuts” is common on software projects. Developers may make suboptimal decisions due to a lack of understanding of the structures of the system, schedule pressures, or perhaps a lack of clarity in the architecture from the start. This kind of deterioration is a form of technical debt, called architecture debt.