I spent some time perusing the programming stacks at Seattle’s main library today, and skimmed through some texts on software architecture. Perhaps the most interesting was 97 Things Every Software Architect Should Know: Collective Wisdom from the Experts (ed. Richard Monson-Haefel). It’s a collection of various two-page thoughts from people who do software architecture from across the globe. Think Chicken …
Building Architecture is a Lousy Metaphor for Software Development: We Need a New One
I think that using Construction as a metaphor has run its course of usefulness. It’s time to get another one.
“database quality has improved little in 11 years…”
For the past eleven years, Blaha and his associates have been reverse engineering software for evaluating products. He came up with some terrifying results.
Stewart Brand showed “How Buildings Learn”, So Why Can’t Software?
In the end, you can’t know what you will need to have at the onset of your project. You can only get the optimized environment after you’ve lived with it and changed it. It follows that you can’t get an optimized environment for tomorrow’s needs until you change it for tomorrow. So, you’ll never be done; you will always need to make adjustments to your environment, or in response to your environment.