敏捷软件开发：原则、模式与实践 (（美）马丁著)（Z-Library）

【One-Line Pitch】 A foundational guide to writing software that stays changeable: it links agile values, object-oriented design principles, and reusable patterns into one practical discipline. Best for developers, tech leads, and students who want design skills that survive real-world change requests. 【Book Arc】 - **Opening (~0%–20%)**: Sets the agile context—why iterative, feedback-driven development changes what "good design" means and how programmers should work day to day. - **Early (~20%–40%)**: Builds the object-oriented foundation: classes, responsibilities, and the principles that keep modules loosely coupled and easy to extend. - **Middle (~40%–65%)**: Moves into design principles in depth, showing how to recognize and fix rigid, fragile designs before they harden into legacy code. - **Late (~65%–85%)**: Introduces classic design patterns as named solutions to recurring problems, connecting pattern choice back to the principles. - **Ending (~85%–100%)**: Applies principles and patterns through worked case studies, demonstrating refactoring and incremental design under realistic constraints. 【Key Takeaways】 - **Agile is a design philosophy, not just a process** (Opening): Iteration and feedback only pay off if the codebase can absorb change; agility and design quality are inseparable. - **Principles are the "why" behind patterns** (Early): Patterns are useful only when you understand the forces they resolve—memorizing pattern names without principles leads to over-engineering. - **Coupling and cohesion drive maintainability** (Early): Keeping responsibilities well-placed and dependencies controlled is what makes software cheap to modify later. - **Design smells signal deeper problems** (Middle): Rigidity, fragility, and immobility are symptoms; the fix is restructuring dependencies, not patching symptoms. - **Patterns are vocabulary for teams** (Late): Shared pattern names let developers communicate design intent quickly and review each other's work more precisely. - **Design happens continuously** (Ending): Case studies show design as an ongoing activity woven into development, not a one-time upfront phase. - **Refactoring is how design improves safely** (Ending): Small, behavior-preserving steps let you evolve structure while keeping tests and feedback intact. 【Reading Tips】 - Read the principles sections slowly; they carry the most transferable value and are easy to skim past. - Treat the pattern chapters as a reference—deep-read the patterns you actually encounter, skim the rest on a first pass. - Work through the case studies actively: pause and predict the next refactoring step before reading on. - Keep a note of design smells you recognize in your own codebase; that turns theory into practice fast. - If you already know basic OO, you can move quickly through the early chapters and slow down at principles and case studies. 【Coverage Limits】 The available excerpts contain only the book's title and author metadata, so this guide describes the book's well-known structure and themes rather than verified chapter-by-chapter content. Specific examples, code listings, and chapter titles are not covered by the excerpts.