• Stanford's iPhone development course.
  • "Is writing ever NOT collaboration? Doesn’t one collaborate with oneself, in a sense? Don’t we access different aspects of ourselves, different characters and attitudes and then, when they’ve had their say, switch hats and take a more distanced and critical view — editing and structuring our other half’s outpourings? Isn’t the end product sort of the result of two sides collaborating? Surely I’m not the only one who does this?" Something else that's been on the pile (to link) for a while now.
  • "The craftsman as hero is a consistent motif in Ruskin’s artistic and social theories. To him, mechanisation and division of labour dehumanise workers, enslaving them to execute exactly the specifications of others. The only way to recapture the humanity in labour is to put the designer back in touch with the tools of the craft and to unleash the creativity of the maker." A lovely metaphorical piece from Matt Edgar, reminding me of how much I need to brush up on my knowledge of the Arts and Crafts movement, if only because of how much I appreciate their sentiments.
  • "At some point, I begin to feel that I am carrying entire Latin American forests home with me. Also, I am afflicted with a terrible need to stop and write things down, at almost every corner, slowing my passage through the city and impeding motion. I am locked in this ridiculous two-step, unable to travel more than half a block before sitting down and writing out more, papering over the last thirty feet, dripping more ink onto the street: this absurd project, this incomprehensible, incompletable urge, this terror of forgetting and compulsion to record." Beautiful writing from James, which has been sitting on the "to link" pile for far too long.
  • "Here is an extraordinary piece of film. It is a live outside broadcast of a British army simulation of an attack on a train in Britain. It went out at prime time on a BBC programme called Saturday Night Out. And it happened in 1956."
  • "Maps are having their F-64 moment, right now, which is important and wonderful but I don't think anyone really wants to live in a world with an infinite depth of field. It's an appealing idea but then something like the Hipstamatic comes along and we all get irrationally weak in the knees, all over again." As usual with Aaron, I could quote most of the article, but in this case, I'll pick my favourite piece of writing, rather than perhaps the most succint quotation; just read the whole thing. (And: I wish I could code or even write like this).
  • "No huge surprises, except maybe that I changed to dark toolbars. No multi-column reading, no fake book-page animations, and no giant newspaper graphics." Great explanation of Instapaper on the iPad from Marco. And: I'm sure it'll be great; in the past two months, I've become a total Instapaper convert.
  • "I see Valve Software today holding the same position in the overall media landscape that Marvel Comics occupied in the early-mid 1960s. In both cases, we have two experienced studios, neither the mainstream-recognized giants of their fields, who made an unusual decision: they chose to spend the creative capital gained from prior commercial success to quietly revolutionize their respective medium's dominant genres, rather than take the safer path of grinding out more derivative sameness."
  • Ben Zeigler's notes on Bunge's Jaime Griesemer's talk at GDC, all about balancing. Sample quotation: "It can be tricky to balance, because designers can misinterpret competence (getting good at a weapon) with the weapon being balanced. We CANNOT use our intuition at this stage because it will lie to us. Changes will have to be done in larger batches, and we need to avoid bias effects." Really, the whole thing is jampacked with interesting stuff (not all of which I agree with, but most of it is very good indeed).
  • "…let's not kid ourselves. If you sell a game that's a first-person shooter, then no matter how many RPG elements you shoe-horn into the game, the shadow that hangs over every character interaction that you have, no matter who they are, is the question in the player's mind of "What happens if I shoot this person?" And that's our own fault! We've sold the player that; we've made a contract with the player that says it's okay to kill people. Why would we then chastise them for exploring that?" Patrick Redding is brilliant. This interview, with Chris Remo on Gamasutra, is great – Remo asks some smart questions, and Redding gives some really smart answers.
  • "The game insists that I focus, even for mundane activities like carrying groceries, on carefully following directions delivered to me visually on-screen. The simple act of carrying groceries is subsumed by the mechanical procedure of executing a series of prompts _for no apparent reason_. This, for me, is the primary disconnect in Heavy Rain. My mechanical game-directed actions don't amplify or add meaning to the in-game behaviors they execute. They don't pull me in; they keep me out. " Hmn. I've been thinking about something similar recently. Time to fire up the blogpostmatron…
  • Lovely, lovely article explaining just how the PeepCode Blog works. The blog itself features unique layouts for every post. There's no CMS, no database, but what's going on under the hood is at least as clever – and the flexibility makes the beautiful and clear pages much easier to build.
  • "…for reasons that baffle me, my TV can only receive the four terrestrial channels, plus a grainy feed from the building’s security cameras. Easy choice."