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
I recommend eating chips An Essay by Sam Anderson www.nytimes.com Join me. Grab whatever you’ve got. Open the bag. Pinch it on its crinkly edges and pull apart the seams. Now we’re in business: We have broken the seal. The inside of the bag is silver and shining, a marvel of engineering — strong and flexible and reflective, like an astronaut suit. Lean in, inhale that unmistakable bouquet: toasted corn, dopamine, America, grief! We are the first humans to see these chips since they left the factory who knows when. They have been waiting for us, embalmed in preservatives, like a pharaoh in his dark tomb. Looking Closely is EverythingOne brick seeingdetailsfood