Artsy Techie

Mix Web Technology, Art, Culture. Bake Until Crispy

Hello!
My name is Olivier Thereaux and this is where I write about Life (and my work in design, Web technology and innovation), The Universe (mostly culture, art and travel) and Everything.

Inception’d

A word of warning: if you have not seen the movie Inception, you may be wary that the following could include storyline spoilers. Not quite. Even if you fully read and understand what follows, you will still have no clue what happens through the movie, and I will not spoil your experience. You may however skip the links until you have seen the movie, as they would not make much sense anyway.

528 491

At a turning point in the movie, we are shown a room where a dozen people, all hooked to a machine that lets them share a collective dream, come to sleep a few hours every day.

Those people are us.

They are sleeping in what looks very much like an opium den with wires in lieu of pipes and smoke. We learn they are addicted, no longer capable of dreaming on their own; they chose the reality of the shared dream over whatever their life may be like.

Ever wondered how much time our contemporaries, on average, spend per day hooked to our televisions? They are us. Or rather, they are a projection of how Inception’s director Christopher Nolan sees us: hooked to the machine 3 to 4 hours a day, dreaming a collective dream architected by the people in Hollywood, incapable of dreaming our own dreams any more.

Once you go down this rabbit hole and start seeing the whole film as a film about film (need to go deeper?), there is no turning back. If you start thinking this way, you’ll wonder if there is a reason why all location (but one – Casablanca) where Inception was shot are icons of mass culture: Los Angeles (Hollywood), London (The mighty pinewood studios), Paris (temple of high culture) and Tokyo (Gross National Cool). And isn’t Rupert Murdoch Australian, just like the character of energy mogul Fischer in the film?

I left my first viewing subscribing to one of the most the widespread theories about the story line.

I was wrong. Hint: the spinning top topples twice – in Tokyo and Paris-. And a half. Draw your own conclusions.

But I was also on to something: how the story ends for the characters of the movie actually doesn’t matter. The last shot of the movies shows us a piece of information that may or may not help us decide what is real and what is not. And you know what? The characters are no longer in the room, no longer looking at the artefact. They don’t care. The question is not theirs any more.

The question remains, not for them, but for us. And we’ve been asked the question many times before – we just didn’t notice. Why would an actor look straight at the camera and ask: “what do you believe is real?”. This, happening on the screen, or whatever awaits you when you get up, stretch you legs, rub your eyes and get back to your life?

Two feet watching TV

Inception – the subtle and difficult art of planting an idea in someone’s mind while thy are deep in an altered state – is indeed performed throughout the movie. On us. And the simple fact that we all come out of the theater discussing for hours and days about what happened to Cobb (the main protagonist of the film, played by Leonardo Di Caprio) means that Christopher Nolan and his team have succeeded.

Fixing the Bus System

What happens when one person moves on her own to an unknown major city is a fascinating way to observe (and hopefully help fix) things that are broken in our urban systems. Newcomers have to go through a period of fairly stressful learning and adaptation to the new city. Any system that is not welcoming or easy to understand for a “native” of the city will also systematically be a major bag of hurt for the rest of us, the impact of bad service design multiplied manifold.

This is true for tourists and travelers, and acutely so for immigrants: while an issue is likely to be shunned by short-term visitors when they can simply avoid it, immigrants are bound to have to deal with it sooner or later.

One could think that language is the main barrier against the integration and adaptation of new inhabitants of a city. Indeed, it took me months, sometimes year, before I approached some institutions of Japanese life without a wince, and language was a large part of the problem. In the near decade that I spent there, I became rather comfortable and acquainted with things such as ordering stuff on the phone, explaining my situation to immigration officials, or going apartment hunting. Visit to Japanese doctors, however, remained to the end a puzzling, stressful and often degrading experience. After so many years, I don’t think the language barrier was the issue any more. The truth is, the doctor-patient relationship in Japan is horribly broken, or rather, it is so entirely alien to my cultural framework that I never quite learned to accept it.

After moving on my own to 4 large cities in the past 15-ish years, and visiting quite a few more, I can start to list a number of behavior patterns which say a lot about myself, obviously, but also about the urban systems. As a puzzled, stressed and curious newcomer, whether I quickly and fully embrace a system, or whether I avoid it for a long time is an interesting measure of how “usable” the system is.

Fare information screen at the front of a typical Japanese bus

Take public transportation for example. I have lived in Rouen, Paris, several cities in Japan, and Montreal – all with both a tram/metro system and bus system. In each case, being happier as a pedestrian than a driver (a much better way to discover a new city, incidentally) from day 1 I was taking the metro, walking around, hailing cabs on occasion. I never took a single bus in Rouen. I only ever took the bus twice in Paris, always because I was tagging along with a friend. In Japan, except for the bus that was the only way to get to my workplace, it took me months before I took buses to go around on a regular basis. Ditto for Montreal.

Why?

Set aside the easy explanation that in any country, the odds of ending up with a grumpy, mumbling bus driver is fairly high. You get wonderfully helpful bus drivers everywhere, too. I think the explanation goes deeper: the bus system in every city I know is broken, hardly usable, and we hardened urbanites only cope with it because we’re so used to it. Here are a few symptoms of the brokenness, which could be tackled fairly easily.

  1. The bus system is inconsistent from place to place:How is one supposed to queue? Is one to get on the bus through a specific door? Does one have to pay when entering the bus, when arriving at destination, or at some point in between? These questions aren’t merely rhetorical, and most combinations of answers actually mirror the reality in one city or other.
  2. The bus payment system is as complicated as it is hurried:Unlike the metro systems, where payment is generally made at a time reasonably disconnected from the ride itself, payment for the bus is often required just as one enters the carriage, or as one leaves. Ever had to wait (preferably, in the pouring rain) for a tourist to figure out how much and how to pay the ride before you could enter? Ever had to fumble in your pockets for the exact amount – in small coins – required to get on? And I am not even mentioning the many places with a variable bus fare.
  3. The bus grid is hardly ever mapped:Even assuming that one city has a single public transportation system, and not, as is the case in e.g. Tokyo, a myriad of small-ish private transportation companies loosely connected throughout the urban network, it is rare to find an intelligible map of the bus network for the whole city.The mesh of bus routes and connections in most major cities is too large and intricate to be easily charted on a mid-sized map, yet this is the only map you are likely to get.
  4. (not) Knowing where or when to get off is stressful:This used to be a consistent terror of mine when I used to start using buses in foreign countries: given that I often have no idea what the place I am going to looks like, how am I supposed to know when to get off? How am I supposed to know sufficiently early so that I press the button/pull the chord/holler at the driver early enough? And since the bus is not alway halting at stops unless it has to, I might entirely miss my stop and end up in the middle of nowhere.The Japanese bus system, for all its strange intricacies, has found a solution to this: a marquee screen in several locations in the bus display the current location and next stop, and a voice announces where the bus could stop next. The solution is indeed costlier than forcing grumpy drivers to grumble that information, but the ever-pragmatic Japanese companies have found a way to offset the cost: between stops, the pre-recorded voice will also spew “useful” (and paid for) information about some of the shops nearby.

Granted, contemporary technology for a first-world traveler will mitigate, or sometimes even void, such issues. Who cares if the transportation is hardly usable when one can research its tricks in advance, find out in real time when the next bus is supposed to pass or use a map application on a mobile device to calculate the best itinerary and follow one’s location at every moment?

Yet I find these tech solutions unsatisfying. I find them costly, lazy, unfair, providing only solutions for the rich tourist and the tech-savvy. They make me re-think my reaction to Adam Greenfield’s Read-Write Urbanism post, which at the time had me think “what’s the point of building connected, smart urban appliances when you can provide smart applications on mobile phones”. I may have been wrong – there is value in creating solutions for all, directly in the fabric of the city.

Indeed, there are quite a few solutions to the problems I noted above; some are already implemented in some urban transportation systems (for example, the display-and-speech info on the next stop in Japanese buses), others are mere ideas waiting to be developed. Let’s try to document these ideas and initiatives in comments below.

Men at Work

The back-alley of my Montreal appartment has been, for the past month, an observation deck to the work of three different crews adding an extra floor to buildings on the other side of the alley – going from two storeys to the more Montreal-usual three.

The whole spectacle is rather fascinating: the grunts, curses and shouting. How bricks and planks are neatly piled onto a shelf ingeniously sliding on a ladder. How the work area is protected from the occasional outbursts of bad weather that are bound to happen in the span of a few weeks.

Most enlightening is the realization that in order to add a new floor to a building, one mainly has to add a new roof.

Going to Paris Web 2010!

Here are three reasons why I am completely in love with the team behind the Paris Web 2010 conference.

They specifically allow multiple proposals in their call for speakers

This is good news for people like me, constantly shifting between disciplines and generally pursuing several big topics of interest at a time. I’d not had a chance so far to go to the conference: even though the paper I co-authored last year had been selected, I eventually ran into some schedule conflict and the other co-author went and delivered alone. This explicit invitation to submit multiple entries meant that I could suggest a conference on innovation, a mini-conference about web standards adoption, and a workshop on ubiquitous techs, and not worry about which would be more appropriate than the others.

They didn’t flinch when they saw me sending in different topics

In retrospect, I should probably have guessed that they were expecting experts to suggest several sessions in different formats (conference, workshop, mini-conference) in the same area of interest. This is how the amazing Denis will be presenting three different sessions on Web Accessibility throughout the conference.

They’re inviting me to speak!

I will be giving a talk-discussion on the challenges of innovation in an organization dedicated to keeping its staff busy and productive – a great excuse to talk about innovation, its history, the frameworks that work, those that don’t…

See you there!

The Peter Principle: Why Most Managers Suck

One of my colleage today discovered the Peter Principle, whereby “in a hierarchy every employee tends to rise to his level of incompetence”. Tongue in cheek, he asked on our team mailing-list whether our company suffered from it.

My answer: of course we are – any company with a hierarchy will be. The main reason is that “promotion” in our industrial society, generally means “You’re really good and experienced at your job? Now stop doing it and start managing a bunch of people”.

And the fact is, most people are really, really bad managers. A manager should be leading by building trust and a culture of excellence/results/you-name-it, mentoring, empowering and setting clear objectives. Instead, when put in such a position, most will fail to build trust – instead they put process over people, waver on objectives, micromanage and bully. Management is hard. Management is the art of losing control.

And if you’re not doing too badly at the middle-management role, wait until you’re promoted to an executive role with the massive responsibilities it involves and the strategic leadership it demands…

Don’t like the sound of this?

  1. Build a team culture where promotion does not necessarily equate management, but “here is a new challenge for you”,
  2. mitigate the negative effects of hierarchy by adopting a less-hierarchical structure and Agile, Iterative and Incremental processes.
  3. …or stay small.

I was once chatting with the architect in a small-ish (20 people) tech company. Asked about the size and structure of their group, he told me “Everybody codes here, except for the accountant and the CEO. The latter used to code, but he was so bad at it, we made him in charge of everything else”.