Monthly Archives: January 2007

Early heads-up: if you happen to be in the NYC area, you may want to block out the evening of the ninth of April. I’ll be giving an entirely new talk, which I am terribly honored to be able to present at the Great Hall of the Cooper Union.

I’ll be debuting my City Is Here For You To Use material; the talk will be followed by a panel discussion (participants TBD, but bound to draw heavily from the usual suspects) and a reception. I hope to see you there.

So I’m thinking about swapping the Hemingway theme this site is styled with for another. Don’t get me wrong: I think Hemingway is one of the only interesting things to happen to blog design in about five hundred years, a fairly serious aesthetic and conceptual advance.

The trouble is that I don’t like the way Hemingway is configured on WordPress-hosted blogs, one of which this happens to be. You don’t get nearly as much flexibility as the theme is actually capable of offering - e.g., neither the line length of the two lead stories, nor the way they render tags when displayed on the front page, can be customized. And that results in an unacceptable user experience.

By contrast, Hemingway in other hosting environments is far more flexible, and it results in better-looking sites. It can be hacked and tweaked like any other skin, and in the hands of someone with a discerning eye, the results can be lovely: look at what Christina Ray and Joey Roth did with theirs.

If I can’t do something like that, I’d rather at least offer Speedbird in a wrapper that doesn’t impose quite so many constraints. So I’d like to ask you to nominate a few WordPress themes you think might suit. And we’ll take it from there.

In other WordPress news, I figured out how to disable the Snap preview that was driving me crazy (and apparently all of you as well). Enjoy!

And finally, while we’re doing meta, I wanted to welcome a comparative flood of new readers to Speedbird: my bike messenger piece from the other day got picked up by SF Fixed Gear and Bike Forums, from which I got a ton of traffic. (If you follow the links, you’ll see what happens when a dense piece of writing meant for a very few people is encountered by an audience equipped with bullshit detectors locked on “high.”)

OK, that’s enough from me for right now. I’ve got a pile of work and writing to get done before heading to Geneva for LIFT next week. Have fun, and stay warm.

Corpspeak drones: English already has a perfectly good word, “lesson.” Learn it. Know it. Live it.

That is all.

Of all that is written, I love only what a person has written with his own blood.
- Old Fred

I think I mentioned the other day that I’ve been reading Iain Borden’s essential Skateboarding, Space and the City, which I’m enjoying immensely, both as a detailed social history of a domain I’m more than cursorily familiar with, and for the way it frames skating as a performative critique of the urban condition. In Borden’s reading, a skater, in physically addressing the various spaces and surfaces offered up by the city, reclaims them from their ostensible or official purpose, reassembling them into nothing less than an alternative and highly personal telling of place.

We’re not too far, here, from what the Situationists originally meant by “détournement,” but there’s also a delicious, inescapable viscerality to this particular act of appropriation that I recognize immediately. Here’s Borden describing the thrill of skating an emptied swimming pool:

First…skaters encounter the wallness of the wall, sensing how the pool presents itself as a surface changing from floor to wall under their very feet…[T]he higher up they go, the more vertical, the more wall-like that surface becomes. This involves a quadruple movement of body and architectural surface: initially comes the sudden compression of body hitting the bottom curve of the transition, where terrain is felt to press back on the skater, translating momentum into a forced acceleration of his or her trajectory up the wall; at this point the second stage arrives, tense compression is released, and the skater feels the enclosed concave curvature of the transition give way to vertical flatness, and to a corresponding sense of speed and expansivity of space. The third stage is that stalling space-time where the skater reaches the top of the trajectory, hangs momentarily, and begins the kickturn - for the skater, this is a highly physical yet simultaneously fantastical and dream-like experience, where space-time are conflated and frozen into a dynamic-yet-stable instance.

I’ve never done that, but I’ve skated enough to know that Borden gets it just right, in a mode I might call the physical-lyrical. Here, as in the rest of the book, what I like about Borden’s writing is that he appropriately insists on the granular, the momentary, the local and the specific. A material culture can only emerge from a description like this if it’s properly characterized, right down to details like the precise composition of a pool surface and the particular Santa Monica and San Fernando Valley schoolyards first appropriated for skating. (Actually, it doesn’t have a hope at all of so emerging: we all know that these are things that can only be fully understood if lived. Only the most tenuous smear of a subculture’s nature will ever be conveyed to those distant from it in space, time or sensibility. And even then, only if the details are spot on.)

Borden deserves recognition for taking the (occasionally ridiculous) artifacts and cultural apparatus of skating as seriously as any anthropologist ever did a tribe’s rituals and fetishes; I confess that I get a great big kick out of reading a solid ethnographic account of transitions that I lived through, like the shifting fashions in deck widths, wheel durometer readings and graphics that accompanied the turn from pools, ramps and parks to street skating in the mid-80s. But, frankly, one of the things I am enjoying most about Skateboarding is that it has given me permission to re-examine a parallel domain of physiospatial experience which, despite being considered at the distance of what is now quite a few years, might yet shed some light on the broader urban condition: my time as a bike messenger for San Francisco’s Aero Special Delivery.

I hasten to point out I was the world’s worst and least representative bike messenger. What’s more, I enjoyed this status for a mere half-year or so, between my arrival in San Francisco at the tail-end of 1990 and Aero inviting me inside to work order entry sometime around July of the following year. (Hey, it was a much better wage, and I already knew I was no good on the bike, or at least distinctly nonoptimal. What would you have done?)

Notwithstanding the brevity of my experience, I feel that it served to adequately instill in me enough of the messenger worldview, ethos and sense of space/time that I can unapologetically relate some of its essentials to you here.

The messenger and the city

For the bike messenger, the city is a particularly rich and complex terrain, in which anything reasonably smooth and approximately horizontal can become a thoroughfare, however interstitial and whatever its legal designation. Onto this terrain the messenger subconsciously maps the contours of an economic geography - known sources and sinks of courier assignments, or “tags” - and a threat landscape, this latter comprised of blind corners, cable-car and metro tracks, and traffic lanes sufficiently wedged up against parking lanes that the risk of being “doored” is increased.

Bike messengers - or at least those in San Francisco at the very beginning of the 1990s; your mileage, as ever, may vary - are paid by the job. We called this “pulling tags.” The faster, the more cannily you are able to exploit the city’s fabric of possibilities, the quicker you can close out one tag and pick up the next. The upside of this constraint is that it gives rise to an extraordinary repertoire of creative and only incidentally illegal uses of space, in which just about anything can be transformed into circulation. The downside is that a slow or otherwise incompetent messenger can easily reach the end of the day having earned something less, when averaged out, than the legal minimum hourly wage; at one particularly bleak point in my brief career I calculated that I was paying out more in calories than I was bringing in by dollar equivalent.

Key to the messengering proposition, at least in the technosocial milieu obtaining fifteen years ago, was that we were radio-dispatched from a central office. Fitted out with the predictable variety of self-styled sobriquets and callsigns, we wore clunky walkie-talkies fixed to the straps of our bags by elastic webbing, and received from them the stations of our daily transit of the city.

The relationship between a bike messenger and his or her dispatcher is simultaneously curiously intimate, intensely political (your livelihood depends on staying on their good side!) and thoroughly mediated. I worked a solid - efficient and remunerative - month with a replacement dispatcher I never once met in the flesh. I was delighted to see William Gibson attempt to limn this relationship, and just about pull it off, in his 1993 Virtual Light.

As I remember it, the specific magic of the competent dispatcher was to weave together for you a customized and maximally efficient selection from the series of tags crossing his desk in something pretty close to real time, based on what he knew of your current position vis à vis both other available (or soon-to-become available) messengers, and the destination. In this way, he’d impose a coherent narrative on your day, a thread connecting the end of one run with the beginning of the next.

(”He” because my dispatchers, at least, were invariably male; I specify “what he knew” of your position because it was entirely self-reported, which is just one of the many aspects of the messenger experience which cannot help but be undone by the advent of ambient informatics.)

Sometimes, of course, it was politic to fudge your actual location. Some intersections were particularly dense with architectural, engineering or legal practices, television stations, and the like, and you could invariably count on proximity to these to generate a high volume of tags. Either you were angling to pick one of these up when you were properly out of the catchment basin, or - for me, anyway, unusual among messengers in that I generally privileged the prospect of spare time over the three dollars I might pick up over the afternoon’s last tag - dissembling the fact that you were no more than a block from triple-five Cal when a superhot tag lit up the board at ten minutes to six.

It’s only now, with heat maps and other sorts of sophisticated information visualization edging their way into the broad public consciousness, that the bike messenger’s internalized and therefore “intuitive” macro/micro read of the urban surround might find a representational strategy capable of conveying its nuances. For me, it was something that ultimately found its most accurate map in the arrangement of my nerves and muscles.

The messenger’s body

I once described what happens to the body in Basic Training as the “yoga of organized violence,” and so it is here: efficiently linking micromaneuvers like trackstands and bunnyhops (which I suck at) with the larger pattern of drifting and weaving through traffic entrains a certain way of being-in-the-body that I can only think of as the yoga of urban logistics.

As with many varieties of yoga, this one begins with a becoming-conscious. When you’re whipping through a labyrinth of very large, very hard things in unpredictable motion, all too unable to forget that force = mass x acceleration, microfeatures of the traversed terrain and of the bike itself weigh heavily in your situational awareness. An unseen rut an inch across or a marginally underinflated tire can mean a blown tag, even a broken collarbone; coming to recognize the timing of stoplights is all-critical. You learn, and learn quickly, to model the world in four dimensions, to run that model ahead of real time, and to project optimal traverse corridors into and through a situation which is at the threshold of becoming actual.

But that’s all between the ears. That awareness corresponds with another one, this one musculoskeletal: the characteristic patterns of tension and relaxation that take up residence in the messenger’s body. These are stereotypic, keyed to certain stock situations, and once they’ve receded from conscious thought you can string them together pretty fluidly, building an appropriate response to the emergent pattern of fact around you just as you can make of words you use everyday a perfectly valid sentence that’s never before been uttered on earth.

(Some trace of this survives in my body/thinking to this day. Biking crosstown is largely uncomplicated, but it turns out that I have a specific bodily strategy for riding each of Manhattan’s avenues - a trace of which I never became consciously aware, until starting to write this paragraph.)

And finally there physical facts like sunburn, soreness, stiffness, and the persistent feeling of never quite having had enough to eat. These are by no means univocal, in that they speak simultaneously of your poverty and your exposure to the elements, but also of your freedom. And trying to unpack all of that leads inevitably into a consideration of the precise nature of the network(s) the [you+bike] assemblage is embedded in.

The messenger mesh

Here’s where messing really helped me understand something like actor-network theory.

Whenever you utter the words “bike messenger,” you’re really talking about a exemplarily rich domain of activity, in which regalia, patterns of affiliation, codings of class and ethnic origin, nomenclature, etiquettes, syndromes of muscular development (and occupational injury), the manufacture and marketing of bicycles and bicycle components, the economics and technics of dispatch, the perceived need for same-day crosstown transport of distinctly LTL-scaled shipments, the formulation of municipal code, habitual and even stylized patterns of substance ab/use and a whole lot more besides are all folded into one package.

This package is passed whole from person to person every time it’s invoked, and only rarely held up for examination. The human being, the actual messenger, stands as synecdoche for a sophisticated human-machine interface, which in turn lies at the heart of a broader nexus of ideas about cities, transportation and logistics. Sometimes this human being’s hard-won body/knowledge is fed back into the system that implicates him or her, as personal efficiency, as methodological innovation, or as offerings to a shared repository of culture. On other occasions, that system retrieves from individual practice some flag of identity only to mobilize it somewhere down the line as a fully commercialized signifier of notional freedom or rebelliousness. (A mildly interesting article on the popularity of Timbuk2 bags in last week’s New York Times Magazine only scratches the surface of the possibilities here. Full disclosure: I carry a Timbuk2 now, sure. In the day, mine was a Zo.)

Whatever else it means, whatever other functions it serves, though, messing is a way of knowing the city that comes to be written in the sinews and tendons, in the curve of a quadriceps and the permanent scarring where gravel has once embedded itself in the flesh. Having been a bike messenger even for so short a period of time is still and always will be a source of tremendous pride to me, but it’s also something I remember at a level far deeper than words. And (not to get yet another dig in or anything) it’s precisely the sort of possibility this exultant bodily knowledge represents that is foreclosed by any transposition of the urban into the virtual. There is little doubt that there are inequities, frustrations, and imbalances beyond number bound up in the figure of the bike messenger, but I despair to think what cities would be without the specific quality of their exertions.

- Kazys Varnelis drops his conclusion to Networked Publics, awwww yeah. For the record, I agree with him that we’re now into a post-postmodern era; I don’t think it’s yet safe to further characterize it.
- On rereading Aramis. Again, I agree: Latour’s cautionary tale of a systemic failure of will and/or imagination is required reading for urbanists.
- Great seeing Soo-In Yang and David Benjamin present at last night’s Eyebeam confab. I thoroughly endorse their praxis of Flash Research.
- I’m reading Iain Borden on skateboarding, space, and the city, and it’s breaking me heart. At least when I was twenty and poring over copies of Thrasher in a wretched New York City winter, I could look forward to hitting the Brooklyn Banks come springtime and doing my damndest to come aggro. I suppose some thirty-eight year olds have the option. I am not among them.

Can anyone tell me how long after its deployment in a theater of war this will be used domestically, to e.g. disperse protests? I do believe I can hear the LAPD slavering already.

This has been your daily dose of cynicism for Thursday, 25 January 2007.

Apropos of M. Nova’s post on the semiotics of heard events, I wanted to briefly namecheck the use of brief, station-specific melodies as orienting cues by JR East (and, indeed, by other Japanese railways).

These jingles, repeated on the platform throughout the interval between the approach and departure of a train, liminally help a passenger perceive that they’ve arrived at their home station. They tend to the upbeat, in the candy-colored Japanese mode, but many have an undercurrent of weary-salaryman melancholy that I don’t believe I’m projecting onto them.

Don’t believe me? You can buy CDs of the jingles here and have a listen for yourself. Sometimes the otaku impulse is a wonderful thing. (I should also note that these melodies also feature prominently in the notorious Boxes & Arrows piece that set me off last year. And the less said about that, the better.)

This is the year loyalty to a given mobile phone model or manufacturer died for me, let alone using a mobile to announce much of anything about myself to the world. (We’ll see what happens when the iPhone hits.) All I want is for the damn thing to work, to let me make and receive calls. Everything else is gravy. I’ve been using a Nokia 6680 ever since my RAZR expired (two or three days after its warranty did), figuring I’d give them a shot, and it’s been an uneven experience, at best.

On the upside, Nokia has clearly optimized the phone - excuse me: multimedia computer - around taking snapshots. This is by far the easiest phonecam I’ve ever used: flick back the protective cover, with its satisfying detent, and press a big, central, intuitive button. That’s it. Press the button again to take another picture. None of this hunting around for a control that invokes the camera, or stepping through a menu to save an image, the way Motorola does. It’s brilliant.

But you knew there was an “on the other hand” coming, right? The “other hand” with this phone is that it’s unreasonably difficult to use for just about everything but taking pictures - including, unforgivably, making calls. Part of what makes the experience unwieldy is a latency that seems to be inherent to the OS - foundational functionality, such as lists of Received and Outgoing Calls, takes forever and a day to load; you can count it off in seconds. But some of it is clearly, inescapably down to poorly-considered UI choices.

This is not Nokia’s issue alone, of course; I’d say that the standard Nokia UI about splits the difference with the RAZR’s, in terms of what it gets right and wrong. (Now there was an object where every expectation set up by its graceful form factor was thoroughly, comprehensively, almost gleefully undermined by a clumsy UI. If you’ve never used a RAZR, trust me: it was ass.) For whatever reason, though, and probably irrationally, I had expected the Finns to do better.

I’d been prepping a fairly extensive list of pitfalls in the 6680 experience, both to warn you away from buying one, and to provide a public record that designers developing future products Nokian and otherwise might find constructive. But this guy’s laid it all out for me already; even though his comments are specific to the N800 PDA, most everything he says is germane to and resonates with my experience of the 6680.

Something particularly irksome that I don’t think he catches - it may not affect the N800 - is the fact that my phone crashes every time I turn it off. I have to remove the memory card before shutting down to ensure it doesn’t freeze permanently on starting back up. But his underlying point remains sound, and better than sound: even facing significant constraints on memory, speed, and resolution, the designers of the Newton UI got things right that Nokia is still dropkicking twelve years later, on a much faster and more powerful device.

Well, this Windows-grade icon design and user experience just won’t cut in anymore. Not out here in everyday life, not where millions of people who don’t happen to work in the IT department will be confronted with it. Even otherwise intriguing attempts to clean up the mobile experience, attempts that might have impressed me as recently as a few months ago, strike me as coming a day late and a dollar short, especially if their interventions get no deeper than the envelope. I don’t want to sound like some hopeless Apple fanboy, but the bar has been raised. And thank god, right? It’s about time.

Even before a single paying customer has laid hands on it, the iPhone has already changed the terms of the conversation. I’m not even talking about subtle and painstakingly worked out interaction cues and behaviors, though those are surely present, but simple interventions that make a profound difference in how it feels to use something. Like crisp friendly Helvetica in the UI. How difficult is that? And yet it changes everything.

By contrast, the 6680 is a mess. The problems go deeper than the usual emphasis on carrier-friendly non-features - which is, again, an all-but-universal flaw of the mobile experience, and by no means a complaint limited to Nokia. Here’s a fair sampling, not comprehensive in the slightest, of 6680-specific peeves:

- Ringtone selection is buried under Tools > Profiles > [Profile] (thirteen clicks, four clicks, one final click);
- It takes thirteen clicks of two different buttons to turn Bluetooth on or off;
- Sometimes the pictures I take wind up in a location other than the Images folder - and before I figured this out, I thought they hadn’t for some reason been saved to memory at all, and you can imagine how that felt after a day on which I had snapped fifteen or so;
- Above all, when I click “Call” from a name in my address book, I’m asked if I want this to be a Voice Call or a Video Call (!?).

Dealing with the Nokia 6680 on a day-to-day basis is just an unwieldy, time-devouring, attention-requiring, consummately frustrating experience. But for the fact that it does more or less satisfy my minimal requirements, and that I do enjoy taking pictures with it, I would have thrown it out already. It brings me no joy to point any of this out - I figured last year that fully one-third of my friends one way or another have their paychecks cut in Espoo, and anyway I hate hate hate know-it-all “experts” sniping from the safety of their non-involvement - but we should no longer be fooling ourselves that what’s been offered here is in any way acceptable. We can only hope that the iPhone announcement has sent Nokia’s designers, alongside their peers at LG, Sony Ericsson, and Motorola, scrambling to improve their game.

I’ll be going to this on Friday evening, and you should too.

(A tale of everyday heartbreak, with softly Proustian resonance if you want it.)

Tracking down some inbound links just now (as, uh, one does), I stumbled across this image on a WordPress template. It’s just a grid of light and shadow, thrown by a roughly perforated vessel, and nothing more than that. Nothing more than that, and more than enough to knock me pretty badly off balance.

What’s so very powerful about this otherwise simple and uninflected header? It’s just that it reminds me so very much of a ceramic lamp I had and cherished once upon a time, in the upholstered depths of the dot.com. Vaguely trapezoidal in mass, with a hexagonal grid of round holes running down its right side, made by a woman whose name is lost to recall. And here’s the thing: I had forgotten about it, entirely, until I saw that picture in the header.

All I remember about it, really, is that it was British, short-run, artisinal, and exquisite, expensive, and that I loved it a lot. It seems very likely that I bought it on an employee discount, with my very first metroathome.com paycheck. And somewhere in the chaos of prying myself from the wreckage of a stormy relationship, moving first to and then back from Japan, selling one house and buying another, it went missing. And maybe I had to forget it, given what it symbolized.

What is that lamp for me, and that particular pattern of light? It’s 1999 and a time before history broke, it’s the first stirrings of my mature design sense, it’s the first time in my life I could afford to buy something so beautiful, it’s the sun and air of the Berkeley Hills, it’s all the love and futile hope we invest in something we know won’t last. And all that was waiting for me, coiled like some fused and patient weapon, to overmaster me the moment I was made to remember it.

It’s OK, now, really, it is. It took me a few breaths, a few long sips of good strong coffee, a spell of sitting and staring out the window, but now I’m totally fine. But I can’t help but wonder what other little landmines are out there, on the Web and in the world, just waiting for me, coiled in force in the heart of something so simple.

(UPDATE: Holy. Crap. Somehow or other, there survives on the Web a listing of some of the things metroathome.com sold, complete with the Test Pilot Collective-penned logo. This page informs me that the lamp was designed by Julie Nelson. And yes, I wrote that copy.

A few milliseconds with Google and I have the rest of the tale. Apparently there really is such a thing as a global mnemotechnical system.)