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
Levels of Scale Scale refers to how we perceive the size of an element or space relative to other forms around it. All things – a tea cup, a building, language, entire eco-systems – consist of smaller components. It is the relationship of the smaller elements which determines the character and degree of life of the whole. Objects which contain a high degree of life tend to contain a beautiful range of scales within, which exist at a series of well-marked intervals and have clearly recognizable jumps between them. To have good levels of scale, it is extremely important that the jumps between different scales of centers not be too great or too small. Christopher Alexander, The Nature of Order The scale of resolution determines what is seen