Against form follows function An Essay by Andrea Resmini andrearesmini.com I cannot get past the fact that any *designer* who throws that phrase around matter-of-factly, as in “of course form follows function”, comes out as a complete ignoramus. An ignoramus who's not just repeating an 1896 “law” without any clues as to what it means but who also, most poignantly, demonstrates to possess no knowledge of what has happened in design and architecture since Sullivan and Adler contributed to inventing the high rise building and, by extension, much of the world we live in. Useless work on useful thingsForm follows functionForm follows failure formfunctionarchitecture
A grossly obese set of requirements Who advocates in the requirements process for the product itself—its conceptual integrity, its efficiency, its economy, it’s robustness? Often, no one. As often, an architect or engineer who can offer only opinion based on taste and instinct, unbuttressed as yet by facts. For in a classical Waterfall Model product process, requirements are set before design is begun. The result, of course, is a grossly obese set of requirements, the union of many wish lists, assembled without constraints. Usually, the list is neither prioritized nor weighted. The social forces in the committee forbid the painful conflicts occasioned by even weighting, much less prioritizing. Frederick P. Brooks, Jr., The Design of Design Requirements proliferationA Plea for Lean Software features