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
Ambitions for someone else's mind "One of the first things I learned about teaching is that you have to respond to each student individually. You don't start with any idea of what they should be doing, who they're supposed to be, or what their performance level is, and you don't compare them to one another. You simply start with each one of them wherever they are and develop the process from there. "...I would think that the most immoral thing one can do is have ambitions for someone else's mind." Lawrence Wechler & Robert Irwin, Seeing Is Forgetting the Name of the Thing One Sees Student's future, not teacher's pastI can only conceive for you teaching