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
Choose a suitable design and hold to it A basic structural design underlies every kind of writing. Writing, to be effective, must follow closely the thoughts of the writer, but not necessarily the order in which those thoughts occur. This calls for a scheme of procedure. In some cases, the best design is no design, as with a love letter, which is simply an outpouring, or with a casual essay, which is a ramble. But in most cases, planning must be a deliberate prelude to writing. The more clearly the writer perceives the shape, the better are the chances of success. William Strunk Jr. & E.B. White, The Elements of Style Such tortuous syntax