-
"An image a day and an MP3 to go with it, for no obvious reason." And no RSS, so you'll just have to turn up every day. Lovely concept.
-
Wonderful, delightful, charming writing from Duncan Fyfe; this, and the eight chapters that follow it, are pretty essential, and they're nice and brief. Speculative fiction about games, culture, and the future. And fandom.
-
Gosh, that looks lovely – and bonus points for a preview video that films the iPhone, showing the way fingers work on its surface, rather than just showing the results of interactions.
-
"for a while now we’ve been meaning to post some early childhood snapshots of world of goo, to dig deep into our code repository and remember the good ol’ days. the early part of a game’s development is often very enjoyable because things evolve rapidly and there’s a great sense of accomplishment. it’s also a lot of fun to look back at those early days and laugh at what the game use to look and feel like." First in a seven part series, in which 2D Boy walk us through the – playable – origins of World of Goo. Game devs: more like this, please.
-
"This jQuery plugin generates sparklines (small inline charts) directly in the browser using data supplied either inline in the HTML, or via javascript." Nifty.
-
"…when we step into the shoes of that avatar, be it 1st-person, 3rd-person or otherwise, we exit the darkened movie theater paradigm and enter an intricate, performative, exploratory lab of untested ideas and speculation. We enter a playful space that feels and responds much more like a live theater rehearsal than an interactive movie or a triggered series of movie clips." Michael debunks the games-as-cinema analogy with an interesting take that considers them as more like theatre rehearsal.
-
"This is not a book about the VCS, nor breakout, nor video games and video game culture; it is a chronicle of the experience of that entity we might call “the player.” Oddly, there is little I can take from it in terms of approaches to video gaming or thoughts on the VCS Breakout. But it did enlarge my perspective and help me think about physiological, cognitive, and, let us say, monomaniacal aspects of video game play. Nervous, very dreadfully nervous Sudnow has been, but why would I say that he is mad?" Sudnow passed away very recently; I really ought to read his book, more than ever.
-
"[s3fm]… lets anyone run a streaming radio station, with just a folder of MP3s. Put those MP3s in an Amazon S3 bucket, and give your friends the S3 FM link."
-
Matt's talk (in English) from Lift 09, on scientific fiction, stories, and the design process. Good stuff – not too long – and wonderfully filmed: the cameraman focuses on his hands as much as his face, which is just perfect.
-
NeoGAF users band together to make a perfect, eight-stage, LittleBigPlanet rendition of Contra. Remarkable, especially the behind-the-backdrop puppeteering that makes the walking-into-the-screen levels possible. This had better not get a takedown slapped on it, because it's phenomenal.
-
"Perfect gift for any World of Warcraft player or other MMORPGer in general. You get one "main" glass and one "alt" glass. Serving idea: fill your main with your alcoholic beverage and your alt with your chaser since mains are typically stronger than alts." Oh dear. (But: good gag, and dangerous for drinking games).
-
"SFZero is a Collaborative Production Game. Players build characters by completing tasks for their groups and increasing their Score. The goals of play include meeting new people, exploring the city, and participating in non-consumer leisure activities."
-
"One of my enduring passions is exploring graphic design with programmatic and generative systems. While some aspects of design require the skilled hand of the designer, others can be formalized and explored by computer. For those tasks, Mathematica is an exceptional tool." Some lovely thinking around generative design.
-
Gosh, this is beautiful. I watched it, and the world stopped for a moment.
-
"Teams from around the globe have analyzed figures and come up with a secret formula for App Store success. I share these findings today, ABSOLUTELY FREE. Success is made up of: a FLASHLIGHT…. and DIRTY WET FART SOUNDS!!! Tweetie is the only app that bundles together these two incredible features FOR THE VERY FIRST TIME." Amazing. I must get this!
-
You'll need to sign up for Issuu to download it, but basically: it's a zine, it's aimed at men, so it's a men's zine, I guess. Some nice spreads, a consistent tone, and a hand-drawn map. Not ironic, just full of things.
-
"I mentioned I’ve learned some rules of how database apps change over time, now that I’ve done a few dozen. They are:" Some interesting thoughts on how cruft builds up over time in database-backed web apps; I can't say I disagree entirely.
-
"Imagine it: instead of text adventures and MUDs being designed to entertain MIT students and 23-year old computer engineers, they fall into the hands of bored housewives and teenage girls… This time there are romantic text adventures, digital doll's houses, dating games. Card deck games where you collect friends, or Versace. The trend continues and the licences that get picked up are not action movies, but those of popular soap operas: Not just hot teenage stuff like 90210, but Guiding Light, Days Of Our Lives, and One Life To Live. This is a games industry completely different to our own, and yet somehow… plausible." Jim Rossignol on the soap-as-game.
-
Leonard Richardson's talk from QCon, about REST, his work on Canonical's Launchpad and its web service, and some useful history for anyone wanting to contextualise web services as part of the web.
Second Order Effects
15 January 2009
Seth Godin recently wrote about the end of newsprint, and how he frankly didn’t care. I think he’s correct about some aspects of journalism, but to talk about newspapers without talking about actual physical newspapers is crazy.
What will we miss?
All the second-order effects. We’ll miss the daily conversation with the guy on the newstand. We’ll miss the cuttings that our parents and grandparents send us in the post. We’ll miss seeing other articles in our peripheral vision as we read – complete articles with photographs and boxouts, not just headlines – as opposed to the ads that surround the online edition. We’ll miss scrawling notes in the margin. We’ll miss leaving them lying around the flat for our flatmates to read. We’ll not have anything to wipe our shoes on.
I say this as someone who’s happy reading from a computer screen, if not from an e-reader. The second-order effects of newspaper journalism being transmitted in physical newspapers are just as compelling a reason for their existence as the intended outcome.
This reminded me of something else that’s been on my mind, relating to another newspaper; this time, one my friends made.
Russell and Ben’s lovely paper is receiving a slowly escalating amount of attention. I’m glad, because it’s really good, and because there’s a (passable) piece of writing by me and lots of (very good) writing by many of my friends in there.
But I’m curious – and perhaps a bit concerned – as to what others might take away from it.
The most important thing about this isn’t “hey, they printed stuff off the internet“. The most important stuff is all the craft, all the second-order effects it has; the details Ben writes about in his excellent post on designing and making the thing; the tangibility it gives to work we’ve done that our non-technical friends (and especially relatives) might never see; the ease of distribution amongst small, hand-to-hand circles it affords; the way you design for (small) mass production rather than one-offs; the reminder that small-scale print is affordable and doable.
Let’s not forget the importance of the immediate first-order effect: this is a beautiful thing, lovely to hold, great to read, fun to show others. In and of itself, it’s delightful (in every sense of the word).
Russell and Ben are, I think, somewhat correct in their closing comment, that “2009 feels like a year for printing and making real stuff in the real world. Its going to be exciting“, but that’s something to consider with caution: making real stuff, printing real things alone, isn’t going to be enough; you’ve got to have the thought, the details, the affordance of second-order effects as well.
I’m excited, for many reasons, as to what 2009 might hold; I hope there’ll be, for me at least, a sizeable amount of making spread across all manner of media – words, things, screens. And, especially, the things that can’t make up their mind which they are. I’m not fussy, and I still think there are lots of interesting problems on screens to solve.
Whatever I’m doing, though, I’m going to try and remember that it’s not just about the idea, not just about the hey-look-a-thing-ness of it all; it’s about the execution, and the detail, and the thought – and embodying that thought in the final product.
To go back to Seth Godin: that’s what newspapers, real, physical, printed newspapers always did. They had affordance out their earholes, and that’s what we loved them for.
I think I’ve found my (slightly corrupted) mantra for 2009:
think twice, cut once.
-
"Whiskey Media provides fully structured data APIs for the following: Giant Bomb (games) Comic Vine (comics) Anime Vice (anime/manga)". This is a really good page for both explaining what you can and can't do, and explaining what the damn thing is. Wonder how good the data is?
-
"Have you ever wanted to sink your hooks into a gaming database full of release dates, artwork, games, platforms, and other sorts of related data? I'm going to guess that, for the bulk of you, the answer's probably no. But if you're out there wondering what to do next with your developer-savvy smarts, you've got another big source to pull data from. The Giant Bomb API is now available for non-commercial use." Giant Bomb really are doing some pretty interesting stuff, alongside their more traditional content.
-
"Customers seem to respond better to the Sims than all the adventure games ever made combined together. Then there are Bejeweled and Peggle and other game games. Who needs a stink’n story? I prefer making interactive stories." The writer of "Dangerous High School Girls in Trouble", interviewed on RPS, drops an interesting one.
-
"The baseline grid. Oh yes, the baseline grid. Let's be honest this is the sort of thing you know you need to know about. And you do know about, you know, sort of. But. Do you really know about it? Of course you do if you work on a magazine or a newspaper, but when was the last time you used one? I almost re-taught myself how to use a baseline grid. I certainly re-read all about it and it pretty much saved my life." Ben, on the details of The Paper. Good stuff in here.
-
"This is by no means an exhaustive list, just a start. In each of these you’ll find other resources to help you dig deeper." Which, right now, is what I need. For a former front-end-dev, I'm a bit behind the curve.
-
"So we’ve progressed now from having just a Registry key entry, to having an executable, to having a randomly-named executable, to having an executable which is shuffled around a little bit on each machine, to one that’s encrypted– really more just obfuscated– to an executable that doesn’t even run as an executable. It runs merely as a series of threads." Fascinating interview with a smart guy, who at one point in his life, did some bad (if not entirely unethical) work.
-
"I do think that during the coming years we will continue to try to bridge the gap between simulated musicianship and real musicianship. That said, the path there is not obvious: As the interactivity moves closer to real instrumental performance, the complexity/difficulty explodes rapidly. The challenge is to move along this axis in sufficiently tiny increments, so that the experience remains accessible and compelling for many millions of people. It’s a hard, hard problem. But that’s part of what makes it fun to work on." There is loads in this interview that is awesome; it was hard to choose a quotation. Rigopulos is super-smart.
-
"On June 17th, every year, the family goes through a private ritual: we photograph ourselves to stop, for a fleeting moment, the arrow of time passing by." Perfectly executed.
-
"The Bop It commands are called out in different tones. These tones differ from version to version as well. In Bop It Blast, distinct tones are employed by both male and female speakers." I did not know that.
-
"A couple of other examples of this kind of thing we like, are the bookish experimentations of B.S. Johnson, whose second novel Alberto Angelo contains both stream-of-conciousness marginalia, and cut-through pages enabling the reader to see ahead – possibly the most radical act I know in experimental books." Yes! And which I bang on about interminably. I love this stuff.
-
"AlterEgo is a Ruby implementation of the State pattern as described by the Gang of Four. It differs from other Ruby state machine libraries in that it focuses on providing polymorphic behavior based on object state. In effect, it makes it easy to give an object different “personalities” depending on the state it is in." Oh, that could be really handy.
-
Oh gosh this is brilliant.
-
"Simply stick your finger in the hole and a virtual representation appears on the screen. Then you can use your virtual finger to play all kinds of cool mini games… from swinging a panda to having a karate fight with a tiny little man." Um, wow. Although I'm always afraid of putting appendages in boxes I can't see inside, though.
-
I think they're wrong, you know. It's not theatre; it's protocol. Maybe people aren't used to the protocol; if yours is the first app they encounter, they'll think that it's OK to show what passwords are – and perhaps that it's OK to write them down elsewhere in plaintext. Applications have a degree of responsibility for users' interactions across the internet, and quirky and cute as this may be, it's just not the place to demonstrate your shining personality.
-
The Brian Dettmer is beautiful. Also: didn't realise the heart/cube cogs were paper, not wood.
-
"…it's another little example of the way the ipod/iphone is such an attention-demanding device. It doesn't orient to you, it orients to itself." Yes. This is a problem.
-
"The US auto industry is on the verge of imploding. People are losing their homes to foreclosure. And, on the off chance that you had the nerve to try to buy something, credit is almost impossible to come by. It is against that backdrop that I would like to talk about working for free. Why? Because I think it is one of the fastest ways to make yourself a better photographer, whether you are a pro or an amateur."
-
"To the extent that the web is becoming truly ubiquitous, and involves increasingly multimodal paradigms of interaction, it seems appropriate to define a Web standard for representing emotion-related states, which can provide the required functionality." No, it does not seem appropriate. It seems bonkers.
-
Hey, I've been in that relationship too! These made me laugh a lot.
-
"bill. francis. louis – look here. help." Ah, the fun of the farm. It's all coming back to me now.
-
"An almost-real-time, behind-the-scenes look at the assigning, writing, editing, and designing of a Wired feature."
-
"Brands are built…out of culture…out of meanings from culture. In the Volvo campaign, the meaning was safety and symbol for this safety was a little girl. Pretty standard. But this book is interested in new ways to source meaning. Let's look at new, emerging brand tactics." More excellent posts from Grant.
-
"The current browsers, including Firefox, just can’t cut it. JavaScript isn’t fast enough (thereby limiting the UX), browsers are single threaded and they aren’t stable enough. If Google want to challenge Microsoft (or anyone else for that matter) in the desktop space they needed a better platform… Google’s solution is I think much neater – build an open source browser that supports multithreading, fast JavaScript execution and stuff Google Gears into the back end so it works offline." Now that's a good explanation.
-
"So we decided to treat Availabot as a world probe: it was decided that we would take Availabot through to the position of being factory ready, and in the process learn as much as possible about the processes of manufacture, and how to develop these kind of complex products with so many moving parts." And, best news of all: Availabot will be coming to market. Excellent.
-
"…this leads up to a discussion of two things: the OAuth protocol which aims, amongst other laudable goals, to help safeguard users’ passwords, and the distinctly unnerving trend which Jeremy Keith has christened the password anti-pattern, which really doesn’t." A clear, articulate explanation of the issues around authentication.
-
In 2000, a group of seventh-graders were asked to draw what they thought scientists looked like and describe their pictures. Then, after visting Fermilab, they were asked to repeat the exercise. Some of the quotations are genuinely excellent, cf "Some people think that (scientists) are just some genius nerds in white coats, but they are actually people who are trying to live up to their dreams and learn more." Aren't we all?
-
"At GDC 2006 Sony’s Lead Programmer – Tim Moss had talk titled “God of War: How the Left and Right Brain Learned to Love One Another”. I read it, remembered mainly that it was interesting they had used Maya as main tool and kinda forgot about it. Only recently I’ve found out that recording from this session has been made available (for free) as well. You can download it here. Combined together they’re really interesting and I recommend everyone to spend few minutes and listen to it while reading slides." Some interesting stuff – God of War pre-scripts a lot of things that other people might want to do in real time, and as such, makes some stuff simpler, and makes controlling the players' experience easier.
-
A detailed look at various techniques for greebling Lego models.
-
"To me, these bizarre sequences represent adaptations of classical Brechtian stagecraft to video games. The way we interact with a game is different than the way we interact with a staged fiction, and by manipulating the tools specific to game-interaction– the interface and the mission-delivery system– Kojima delivers that sense of alienating weirdness that's the hallmark of the Verfremdungseffekt." I like Pliskin's commentary here – the absurdity of Arsenal Gear was great, and much preferable to the boss-rush that followed it.
-
"The dissertation builds on available sociological approaches to understanding everyday life in the networked city to show that emergent technologies reshape our experiences of spatiality, temporality and embodiment. It contributes to methodological innovation through the use of data bricolage and research blogging 1, which are presented through experimental and recombinant textual strategies; and it contributes to the field of science and technology studies by bringing together actor-network theory with the sociology of expectations in order to empirically evaluate an area of cutting-edge design." Anne Galloway's PhD thesis, now online.
-
A remake of "You Have To Burn The Rope", in the style of an Intellivision game. They've changed an important play mechanic and given the game an entertaining twist ending. Fun.
The latency of software development, pre- and post-launch.
23 February 2007
In a recent post about offshoring development work, Ryan Carson explains that the way you know when you’ve outgrown a freelance developer is this:
Getting bugs fixed and new features implemented starts taking fricken’ forever.
There’s some interesting discussion on the post – about eastern-European wage rates, about freelancing, etcetera – but there was one elephant in the room that nobody really mentioned, and I really think it’s necessary. And that’s this:
once your application is live, everything will take longer.
Whilst you’re in the build process, you can turn on a dime; you can commit new code at a moment’s notice, change the direction of the codebase or even the application, churn out features at a remarkable rate. And, when something doesn’t work (despite having passed the test suite… which you do have, right?), you patch it and move on. It’s a doozy.
Once you’re live, everything changes. You’ve got an active audience using the site – you might even have paying customers. You can’t afford for a single thing to go wrong. New features are no longer about build it, run the tests, check it in, deploy. Your testing on the development box has to be more fastidious. The integration between new functionality and the existing needs to be really well thought through. The design needs to be seamless with that which exists already. And, if it goes live and there’s still one of those totally unforseen bugs… you need to be ready to roll back at a moment’s notice, and put the feature on hold until it’s ready.
This is not new. Some teams are lucky enough to make many deploys daily; most can muster up daily fixes; some might go to weekly. But the effort that a feature requires post-launch is far more than it does pre-launch.
So it’s inevitable – freelancers or no – that the pace of development is going to fall off a bit post-launch. Hopefully, only a bit – but it’s not going to be the same rate unless you’re extremely lucky. You’ve also got to keep your users in mind, and break them into new functionality slowly.
It’s a hard transition, going from the development site to live. To you, as an owner, a developer, it feels like the same product – so the change in pace is a bit frustrating. And it’s important to keep the pace as fast as possible. Some fixes are critical, and need to go out the door the instant they’re done; others can wait a little longer – a day or two, if necessary – for release. It’s a rare, focused, hugely talented team that can splurge out new features like a machinegun.
Now, I’m sure that the problem is compounded by avoiding maintenance contracts (and so having to re-contract and re-hire) and having developers whose time is precious. But it’s always important to bear in mind that the latency of any web software development shoots up post-launch. So if it does: don’t immediately reach for the outsource button. Take stock, have some patience, and see what the product needs – how often it needs to be released, how often it needs to be improved. And then you can make that call a little better informed.
The other golden rule, incidentally, is never deploy on Friday. I hope the reasoning behind that is obvious.