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
Rewarding Curation An Article by Wesley Aptekar-Cassels notebook.wesleyac.com Something interesting about the design of Twitter is that it doesn’t have much of a way of rewarding curation, only authorship. ...I’m inclined to think that the mechanisms of distribution of information are very important, and I think figuring out ways to reward good curation is probably an important thing. ...I don’t really know what the solution is here, but I do think that finding and curating good links and bits of information is useful, and something that should be rewarded more than it currently is. organizationcollectionscontent