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
Haven't you noticed? I remember my mother sitting me down at the age of about five with pencil and paper to draw an acacia tree in the yard while she busied herself with her own sketchbook. After a while she came over to see my efforts. “Splendid! But haven’t you noticed how the trunk narrows as it rises? And see how the branches flatten out sideways, not like that oleander over there, where they all go up at a steep angle. Now don’t rub that one out, just do another drawing to compare with the first one.” Jonathan Kingdon, In the Eye of the Beholder Looking Closely is Everything seeing