Skip to Content
Software Architect's Handbook
book

Software Architect's Handbook

by Joseph Ingeno
August 2018
Beginner
594 pages
22h 33m
English
Packt Publishing
Content preview from Software Architect's Handbook

Situations where YAGNI doesn't apply

YAGNI applies to presumptive features, as in functionality that is not currently needed. It does not apply to code that would make the software system easier to maintain and modify later. In fact, following YAGNI means you may be changing the system later to add a feature, so the system should be well designed for this purpose. If a software system is not maintainable, making changes later may be difficult.

You may come across times where, in hindsight, a change made sooner would have prevented more expensive changes later. This may be particularly true for software architects if the change is architecture related. Design decisions made for architecture are among the earliest decisions made, and having ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Start your free trial

You might also like

Solutions Architect's Handbook

Solutions Architect's Handbook

Saurabh Shrivastava, Neelanjali Srivastav
Solutions Architect's Handbook - Second Edition

Solutions Architect's Handbook - Second Edition

Saurabh Shrivastava, Neelanjali Srivastav
Software Architecture in Practice, 4th Edition

Software Architecture in Practice, 4th Edition

Len Bass, Paul Clements, Rick Kazman
Solutions Architect's Handbook - Third Edition

Solutions Architect's Handbook - Third Edition

Saurabh Shrivastava, Neelanjali Srivastav

Publisher Resources

ISBN: 9781788624060Other