Just enough software architecture
by George Fairbanks · first published 2010
4mentions
3recommended by
4HN commenters
2017–2026first – last mentioned
75% recommend25% neutral
Affiliate links. As an Amazon Associate I earn from qualifying purchases.
…understood (unknown unknowns), which needs to be investigated, even if it turns out not to be a great risk. In agile-speak this is called 'spike solution'. Also see lean architecture methods, such as: - 'Just Enough Software Architecture', by George Fairbanks. - 'Risk and Cost Driven Architecture', by Eltjo Poort.
on “The non-linearity of productivity” ↗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…
on “Making Advanced GUI Applications with Godot” ↗Here is a list so far: - Designing data intensive applications - Just Enough Software Architecture - Domain Driven Design - Tackling Complexity in the Heart of Software (Eric Evans) I recommend this one more than Vaughn Vernon's DDD. - Clean Architecture (Robert Martin) - Fundamentals of Software…
on “Ask HN: Must read applied system architecture articles?” ↗I haven’t seen the risk-driven approach explicitly mentioned here. I think it applies not only to code review, but especially to design. It reminds me of George Fairbanks’ Just Enough Software Architecture. He tells a story about his father, a civil engineer, who didn’t apply every engineering technique he knew when installing a mailbox. He just dug a hole, put in a post, and filled it with concrete. The…
on “Ask HN: How to deal with shipping AI-written code you don't understand?” ↗