How to make architecture decisions
ben-morris.com
How to make architecture decisions
the easiest thing to do in a product is add a feature. People new to design tend to see the world of product as a set of features to build more than an experience to balance, and they rush to add things until they paint themselves in a corner with an encumbered experience that lacks a cohesive purpose. Balancing and integrating takes a lot more eff... See more
Nick Punt • Learning Product Design
once the architecture has been agreed upon, it becomes very costly—for managerial and business reasons—to significantly modify it. This is one argument (among many) for analyzing the software architecture for a large system before settling on a specific choice.
Paul Clements • Software Architecture in Practice, 4th Edition
The research for the State of DevOps Reports from 2013 to 2019 was a cross-population study that spanned over thirty-six thousand respondents over six years. It showed that architecture determined if it was possible for teams to:58 •make large-scale changes to the design of the system without the permission of someone outside the team or depending
... See moreSteven J. Spear • Wiring the Winning Organization: Liberating Our Collective Greatness through Slowification, Simplification, and Amplification
If you lay out your system this way, you can, at a glance, get the holistic view and consider where to draw the line in terms of different releases and their associated objectives.