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
The blind men who felt the elephant It is so easy to fall into the trap of contemplating a city’s uses one at a time, by categories. Indeed, just this—analysis of cities, use by use—has become a customary planning tactic. The findings on various categories of use are then put together into “broad, overall pictures.” The overall pictures such methods yield are about as useful as the picture assembled by the blind men who felt the elephant and pooled their findings. The elephant lumbered on, oblivious to the notion that he was a leaf, a snake, a wall, tree trunks and a rope all somehow stuck together. Jane Jacobs, The Death and Life of Great American Cities The blind men and the elephantThe group of blind mullahs