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
172. Garden Growing Wild Problem A garden which grows true to its own laws is not a wilderness, yet not entirely artificial either. Solution Grow grasses, mosses, bushes, flowers, and trees in a way which comes close to the way that they occur in nature: intermingled, without barriers between them, without bare earth, without formal flower beds, and with all the boundaries and edges made in rough stone and brick and wood which become a part of the natural growth. Christopher Alexander, Murray Silverstein & Sara Ishikawa, A Pattern Language Introduction to PermacultureThe garden is a riotChef's Table: Jeong Kwan naturefarminggardens