重构：改善既有代码的设计（第2版）（异步图书） (马丁·福勒(Martin Fowler) [马丁·福勒(Martin Fowler)])（Z-Library）

【One-Line Pitch】 A practical field manual for making working code easier to understand and change, one small, test-backed step at a time. Best for professional developers, tech leads, and architects who already write code and want a disciplined way to improve existing designs without breaking them. 【Book Arc】 - **Opening (~0%–12%)**: Sets up the core idea that refactoring is systematic, low-risk code transformation, then walks through a full worked example—a theater billing statement—showing how a tangled function is decomposed step by step. - **Early (~12%–32%)**: Explains why refactoring matters (design decay, readability, future modification cost), introduces the catalog format, and covers the first practical moves: extracting functions, naming, and building a test harness before touching code. - **Middle (~32%–52%)**: Moves into organizing data and behavior—encapsulating records and collections, replacing primitives with value objects, splitting phases, and moving functions—while emphasizing small commits and static checks. - **Late (~52%–onward)**: Continues the catalog with more advanced transformations such as removing middlemen, dealing with inheritance, and handling repeated switches and large classes, always tied to code smells and safe sequencing. - **Ending**: Reinforces the habit of continuous, incremental improvement and the social/practical side of refactoring—how to explain it to managers, how to pair on it, and how to keep tests trustworthy. 【Key Takeaways】 - **Refactoring is a controlled, stepwise discipline, not a rewrite** (Opening): each change is small, verified by tests, and committed frequently, which lowers the risk of altering working behavior. - **Code smells are the trigger, not personal taste** (Early): repeated switches, large classes, long functions, and duplicated logic signal where to start; the catalog then offers a matching transformation. - **Good names and small functions are the primary tools for readability** (Early): extracting a function and naming it well lets readers understand intent without reading the body. - **Tests are the safety net that makes refactoring possible** (Early): the book stresses isolating business logic from UI and avoiding shared test fixtures, because flaky tests destroy confidence. - **Data organization deserves as much attention as behavior** (Middle): encapsulating records and collections, introducing parameter objects, and replacing primitives with value objects prevent scattered, error-prone logic. - **Refactoring improves design by removing duplication** (Early): less duplicated code means future changes touch one place, reducing the chance of missing a related edit. - **Refactoring supports code review and collaboration** (Early): reviewing code while refactoring—ideally with the author present—produces concrete, immediately applicable improvements. - **The catalog is a reference, not a novel** (Opening): read the first four chapters fully, then consult individual refactorings only when you need them. 【Reading Tips】 - Read Chapters 1–4 carefully; they give the mindset, the smell vocabulary, and the test-first workflow that make the rest usable. - Treat the refactoring catalog as a lookup reference: skim the names once, then return to a specific entry when you actually face that problem. - Work through the JavaScript examples actively—especially the billing and province/production examples—to see how small steps accumulate. - Pay attention to the “how to talk to your manager” and code-review sections; they address the organizational friction that often blocks refactoring. - Keep a personal list of smells you recognize in your own codebase and match them to catalog entries as you go. 【Coverage Limits】 The excerpts cover the book’s framing, motivation, testing setup, and a representative slice of the catalog (extract function, inline, split phase, encapsulate record/collection, value objects, remove middle man). They do not cover the full 60+ refactorings, later inheritance-focused chapters, or the complete code smell taxonomy in detail.