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
Building is never a straight line You might think that Mario 64 was built with tickets and sprints, but, according to interviews, there was no master plan, only the principles that the game should feel good and be fun. They started with just Mario in a small room, and tuned his animations and physics until he felt nice and responsive. After that, the levels were also created as they went, with the designers, developers, and director going back and forth using sketches and prototypes. Building like this is never a straight line. Ideas and code get left on the cutting room floor because part of innovation is questioning whether what you made should exist. The process is cyclical and iterative, looking something like this. Pirijan Ketheswaran, Why Software is Slow and Shitty pketh.org Follow the funEngineers who love their work agileiteration