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
When our forces are resolved When a person’s forces are resolved, it makes us feel at home, because we know, by some sixth sense, that there are not other unexpected forces lurking underground. He acts according to the nature of the situations he is in, without distorting them. There are no guiding images in his behavior, no hidden forces; he is simply free. And so, we feel relaxed and peaceful in his company. Each of us knows from experience the feeling which this quality creates in us. And for this reason, each one of us can also recognize this quality when it occurs in buildings. Christopher Alexander, The Timeless Way of Building The doctrine of salvation by bricksA sense reflected in the plans happiness