Every developer knows the moment: a "one-line change" that takes a week, a fix that breaks something nobody touched, a module the whole team is afraid of. The problem is rarely the syntax. It is the design. This book shows you how to build software that stays easy to change, from a single method to the architecture of a whole system.
AI can generate code quickly. It cannot reliably decide whether that code belongs in the right module, whether an API contract will survive change, whether a business rule has a single owner, or whether a system will remain understandable after six months of new requirements. The developers who thrive with AI agents are not the ones who merely prompt tools; they are the ones who can evaluate generated solutions, spot hidden coupling, reason about complexity, design stable interfaces, and prevent an AI-generated shortcut from becoming tomorrow’s production incident.
Developers who can already write working code and want that code to be easy to change. Perhaps you work in a business-focused company where design is learned by accident. Perhaps you are preparing for a senior, lead or architect role. Perhaps you have read about SOLID and still wonder when it matters. This book gives you a method you can use on Monday morning. The examples are in Java; the ideas apply equally to C#, Kotlin, TypeScript, Python and other languages.
This second edition is a complete rewrite of Software Design Principles: A Practical Guide (2022), with new chapters on testing, conflicting principles, boundaries and architecture.
Stop fearing the next change request. Scroll up and get your copy today.
"synopsis" may belong to another edition of this title.
Seller: Grand Eagle Retail, Bensenville, IL, U.S.A.
Paperback. Condition: new. Paperback. Your code works. Will it survive the next change?Every developer knows the moment: a "one-line change" that takes a week, a fix that breaks something nobody touched, a module the whole team is afraid of. The problem is rarely the syntax. It is the design. This book shows you how to build software that stays easy to change, from a single method to the architecture of a whole system.AI can generate code quickly. It cannot reliably decide whether that code belongs in the right module, whether an API contract will survive change, whether a business rule has a single owner, or whether a system will remain understandable after six months of new requirements. The developers who thrive with AI agents are not the ones who merely prompt tools; they are the ones who can evaluate generated solutions, spot hidden coupling, reason about complexity, design stable interfaces, and prevent an AI-generated shortcut from becoming tomorrow's production incident.What you will learnThe core principles and their trade-offs: DRY, KISS, YAGNI, coupling and cohesion, separation of concerns, clean code and SOLID, as tools rather than laws.Object-oriented design that protects your business rules: invariants, value objects, composition over inheritance, and polymorphism that removes repeated conditionals.Design for testability: reproduce a double-charge bug in a test that runs in milliseconds, prefer fakes to brittle mocks, and change legacy code safely.What to do when principles conflict: eight common conflicts, and the questions that settle them.Boundaries, data and APIs: error contracts, idempotency, pagination, versioning, authorization, transactions, migrations and caching.From requirements to architecture: measurable quality goals, modular monoliths, ports and adapters, circuit breakers and decision records.Communicating design: the diagrams that pay off, the C4 model, and diagrams the build keeps true.Soft skills for design decisions: explain technical risk in money and customers, write a one-page proposal, review designs without conflict, and turn disagreement into a decision.Inside the book11 chapters in three parts: Changeable Code, Changeable Systems, Design in PracticeThree case studies that start from a blank page: a buyer-supplier system, a restaurant ordering API and a B2B product integration70 figures drawn for this editionExercises and checklists in every chapter, plus a one-page design review for your next code reviewA "from symptom to principle" guide, a glossary and recommended readingComplete, tested Java 17 code on GitHub, chapter by chapter, with no frameworks in the wayWho this book is forDevelopers who can already write working code and want that code to be easy to change. Perhaps you work in a business-focused company where design is learned by accident. Perhaps you are preparing for a senior, lead or architect role. Perhaps you have read about SOLID and still wonder when it matters. This book gives you a method you can use on Monday morning. The examples are in Java; the ideas apply equally to C#, Kotlin, TypeScript, Python and other languages.This second edition is a complete rewrite of Software Design Principles: A Practical Guide (2022), with new chapters on testing, conflicting principles, boundaries and architecture.Stop fearing the next change request. Scroll up and get your copy today. This item is printed on demand. Shipping may be from multiple locations in the US or from the UK, depending on stock availability. Seller Inventory # 9798161952931
Seller: PBShop.store US, Wood Dale, IL, U.S.A.
PAP. Condition: New. New Book. Shipped from UK. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000. Seller Inventory # L0-9798161952931
Seller: California Books, Miami, FL, U.S.A.
Condition: New. Print on Demand. Seller Inventory # I-9798161952931
Seller: PBShop.store UK, Fairford, GLOS, United Kingdom
PAP. Condition: New. New Book. Delivered from our UK warehouse in 4 to 14 business days. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000. Seller Inventory # L0-9798161952931
Quantity: Over 20 available
Seller: CitiRetail, Stevenage, United Kingdom
Paperback. Condition: new. Paperback. Your code works. Will it survive the next change?Every developer knows the moment: a "one-line change" that takes a week, a fix that breaks something nobody touched, a module the whole team is afraid of. The problem is rarely the syntax. It is the design. This book shows you how to build software that stays easy to change, from a single method to the architecture of a whole system.AI can generate code quickly. It cannot reliably decide whether that code belongs in the right module, whether an API contract will survive change, whether a business rule has a single owner, or whether a system will remain understandable after six months of new requirements. The developers who thrive with AI agents are not the ones who merely prompt tools; they are the ones who can evaluate generated solutions, spot hidden coupling, reason about complexity, design stable interfaces, and prevent an AI-generated shortcut from becoming tomorrow's production incident.What you will learnThe core principles and their trade-offs: DRY, KISS, YAGNI, coupling and cohesion, separation of concerns, clean code and SOLID, as tools rather than laws.Object-oriented design that protects your business rules: invariants, value objects, composition over inheritance, and polymorphism that removes repeated conditionals.Design for testability: reproduce a double-charge bug in a test that runs in milliseconds, prefer fakes to brittle mocks, and change legacy code safely.What to do when principles conflict: eight common conflicts, and the questions that settle them.Boundaries, data and APIs: error contracts, idempotency, pagination, versioning, authorization, transactions, migrations and caching.From requirements to architecture: measurable quality goals, modular monoliths, ports and adapters, circuit breakers and decision records.Communicating design: the diagrams that pay off, the C4 model, and diagrams the build keeps true.Soft skills for design decisions: explain technical risk in money and customers, write a one-page proposal, review designs without conflict, and turn disagreement into a decision.Inside the book11 chapters in three parts: Changeable Code, Changeable Systems, Design in PracticeThree case studies that start from a blank page: a buyer-supplier system, a restaurant ordering API and a B2B product integration70 figures drawn for this editionExercises and checklists in every chapter, plus a one-page design review for your next code reviewA "from symptom to principle" guide, a glossary and recommended readingComplete, tested Java 17 code on GitHub, chapter by chapter, with no frameworks in the wayWho this book is forDevelopers who can already write working code and want that code to be easy to change. Perhaps you work in a business-focused company where design is learned by accident. Perhaps you are preparing for a senior, lead or architect role. Perhaps you have read about SOLID and still wonder when it matters. This book gives you a method you can use on Monday morning. The examples are in Java; the ideas apply equally to C#, Kotlin, TypeScript, Python and other languages.This second edition is a complete rewrite of Software Design Principles: A Practical Guide (2022), with new chapters on testing, conflicting principles, boundaries and architecture.Stop fearing the next change request. Scroll up and get your copy today. This item is printed on demand. Shipping may be from our UK warehouse or from our Australian or US warehouses, depending on stock availability. Seller Inventory # 9798161952931
Quantity: 1 available
Seller: AHA-BUCH GmbH, Einbeck, Germany
Taschenbuch. Condition: Neu. Neuware. Seller Inventory # 9798161952931
Quantity: 2 available