知识卡片
单步提取后检查局部与整体
选一块有职责的逻辑,建立具体输入输出测试,提取命名函数并替换调用,再运行原基线检查。每步保持可工作,错误时较容易定位;若累积多天破损才验证,已经失去小步重构的主要保护。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
- · 重构与技术债
原书出处 · 1 处
- · 查看原书依据
6. Refactor iteratively. This is where you iteratively decompose a problematic codebase into modular, reasonable, tested components. In the refactoring cycle, you: Identify a block of code to extract Write a unit test and watch it fail (the test will be red) Make the test pass (the test goes green) Import and use a new function Ensure characterization tests are passing Commit changes It’s important
参考来源
- 位置:《Effective Machine Learning Teams (David Tan, Ada Leung, David Colls)》第08章《重构与技术债》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Effective Machine Learning Teams (David Tan, Ada Leung, David Colls)/_epub-src/OEBPS/ch08.html)
- 结论依据:摘录中关于单步提取后检查局部与整体的定义、比较或条件支撑卡片;原书表述不严谨的范围已在覆盖记录逐项限定,不把案例结果外推为普遍结论。
- 原始内容:6. Refactor iteratively. This is where you iteratively decompose a problematic codebase into modular, reasonable, tested components. In the refactoring cycle, you: Identify a block of code to extract Write a unit test and watch it fail (the test will be red) Make the test pass (the test goes green) Import and use a new function Ensure characterization tests are passing Commit changes It’s important