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
Recognizing Constraints An Article by Jeremy Wagner css-tricks.com Super Nintendo games were the flavor of the decade when I was younger, and there’s no better example of building incredible things within comparably meager constraints. Developers on SNES titles were limited to, among other things: 16-bit color. 8 channel stereo output. Cartridges with storage capacities measured in megabits, not megabytes. Limited 3D rendering capabilities on select titles which embedded a special chip in the cartridge. Despite these constraints, game developers cranked out incredible and memorable titles that will endure beyond our lifetimes. Yet, the constraints SNES developers faced were static. You had a single platform with a single set of capabilities. If you could stay within those capabilities and maximize their potential, your game could be played—and adored—by anyone with an SNES console. PC games, on the other hand, had to be developed within a more flexible set of constraints. I remember one of my first PC games had its range of system requirements displayed on the side of the box: Have at least a 386 processor—but Pentium is preferred. Ad Lib or PC speaker supported—but Sound Blaster is best. Show up to the party with at least 4 megabytes of RAM—but more is better. constraints