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 skill of perception The newborn baby and the [blind man suddenly gifted with sight] do not have to learn to see. Sight is given to them. But they do have to learn to perceive. Perception is learnt and learnt slowly. Skill is required for perception as for speech. We are largely unaware of the skill we exercise. None of the things we have to learn to perceive are self-evident, or, apparently, instinctively evident. No doubt, however, we have an instinctive aptitude for this learning, and once we have learnt we cannot easily see as though we had not. As Ruskin says, one has to strive, if one is to see with the 'Innocent Eye'. David Pye, The Nature and Aesthetics of Design The innocence of the eyethe innocent i seeingperceptionlearninginstinct