George Fairbanks's book _Just Enough Software Architecture: A Risk-Driven Approach_ comes to mind. Fairbanks points out that there's risk in every design. How

George Fairbanks's book _Just Enough Software Architecture: A Risk-Driven Approach_ comes to mind. Fairbanks points out that there's risk in every design. How much it should influence your architecture depends on how much it matters to your project. He uses the example of installing a mailbox. You shouldn't approach that with the same level of planning you'd use to architect a building. They're similar projects in some sense, but risk with the former is so much lower that it isn't worth it. In this case, for some projects, the risk of low accessibility might be significant enough that it should be high priority. For others, dependency churn or framework bloat might be higher. Or tooling capabilities. It depends on what you're building.