A practitioner's personal framework for making software architecture decisions, structured around four questions: WHY (understand business vision and money flow), WHAT (model the business workflow using collaborative tools like Event Storming), HOW (identify patterns and solution classes that meet requirements), and WITH (select specific tools matching team skills and constraints). Key principles include designing for removability over maintainability, recording decisions with context and rejected alternatives, expecting decisions to be wrong and planning for change, and collaborating with business stakeholders rather than architecting in isolation.
2 Impressions