知识卡片
用变更频率寻找改造杠杆
遗留系统的改造点不总显而易见。版本控制中的频繁变更区域与构建时的复杂度数据,可帮助定位持续消耗维护成本的模块;再结合业务目标判断是否值得先重构,不能只按代码热度排序。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- · 查看原书依据
have inherited a codebase or system. For this situation, books such as Adam Tornhill’s Your Code as a Crime Scene (Pragmatic Bookshelf) will prove useful for understanding your code and applications. Related tooling can be very useful, such as version control system churn detection utilities that locate constantly changing parts of a codebase, or software complexity measuring tooling that analyzes a codebase or service with
参考来源
- 位置:《Mastering API Architecture》第8章《Redesigning Applications to API-Driven Architectures》之《Identifying Change Leverage Points within a System》(源文件:_epub-src/OEBPS/ch08.xhtml)
- 结论依据:原文指出继承系统时改造杠杆点难识别,并建议用变更频率和复杂度工具寻找线索。
- 原始内容:have inherited a codebase or system. For this situation, books such as Adam Tornhill’s Your Code as a Crime Scene (Pragmatic Bookshelf) will prove useful for understanding your code and applications. Related tooling can be very useful, such as version control system churn detection utilities that locate constantly changing parts of a codebase, or software complexity measuring tooling that analyzes a codebase or service with