Crossing the Chasm

On November 23, 2010, in Computers, by peterb

Thomas at Mile Zero recently wrote a piece called The Console Model is a Regressive Tax on Creativity. I think Thomas is wrong. Here’s my reply.

Thomas,

Your attempt at a conceptual leap from “There exist platforms that limit the amount of hacking that can be done” to “Those limitations are a barrier to entry for minorities” rivals Evel Knievel’s storied jump over the Snake River Canyon, and ultimately it is no more successful.

First off, encoded in your article are the following assumptions:

…that coding or “hacking” is the most meaningful way to interact with technology.

…that “running homebrew code” is a valuable form of experimentation for a statistically significant number of people.

…that making a platform more amenable to end-user coding is cost-free (and here I’m using “cost” not in the monetary sense, but in the sense of “cost to the end user in terms of the usefulness of the platform”).

All three of these assumptions are not simply incorrect, but woefully so. To borrow the words of Wolfgang Pauli, “This isn’t right. This isn’t even wrong.”

Regarding the first assumption: while those of us in the technology sector like to romanticize our early experiences with our various Apple IIs, TRS-80s, and other hackable platforms, the fact is that the skills we learned from doing that work had a narrow effect: they made us marginally more likely to enter into one particular career track in the tech industry. There are thousands of other equally valid, fulfilling, and financially rewarding career tracks in the tech industry that don’t involve the specific aspects of software development you are rooting for. Put another way, the assumption that hacking is an intrinsic good in and of itself seems to me morally equivalent to bemoaning the fact that most people who buy modern cars aren’t using them to brush up on their auto mechanic skills.

Regarding your second assumption: to the extent that one decides to make the (incorrect) choice that Everyone Should Be A Computer Engineer, it’s not clear to me that bemoaning the existence of less-hackable platforms is in any way effective. Risking a second analogy, you are complaining that it’s hard to use hammers as screwdrivers, and really, those hammer manufacturers are holding us back by not putting a Phillips-head socket on the handle.

Regarding your third assumption, end-user electronic appliances have expected use cases. Presumably, both the people selling these devices and the people spending money on them think that these use cases are important. Making a platform “hackable” is not simply a matter of “don’t put DRM on it”. In many cases, what you call “hackable” I call “dangerous”, in the sense of a gun manufacturer who sells a handgun without a safety. If leaving a platform “open” or “hackable” means that developers should compromise the experience of 98% of their users for the benefit of the 2% of users who desperately want to use their hammers as screwdrivers, then I have to say that “open” sounds like perhaps one of the worst ideas I’ve heard of. If, on the other hand, you’re positing that we should refuse compromise, and perfectly meet the needs of 100% of everyone, and make an open platform that in no way compromises the user experience, then I look forward to eventually eating and/or cleaning my kitchen with your combination floor wax/dessert topping.

In summary: even if I accept the (flawed) premise that “careers in technology” are driven by, specifically, the ability to write software, you have in no way made the case that degrading people’s experiences with technology is the best way to get them to write more software. Optimizing technology for openness is almost never free, and if in making a product more hackable you end up interfering with the job the product was intended to do, you will, in the long run, do more harm than good.

Open platforms will always exist. This is a good thing. Equally important is that there will always be platforms whose primary concern is that of the experience of the user, and not the desires of the tinkerer. To elevate the tinkerer’s needs above the needs of those who need the product is, to be blunt, vaguely silly fetishism of technology as an end in itself.

 

4 Responses to “Crossing the Chasm”

  1. Thomas says:

    And since I guess we’re duplicating effort today, I’ll restate my comment here: I don’t know whose post you’re responding to, but it’s certainly not mine. I have made few, if any, of the arguments you’ve attributed to me, and so I don’t quite know how to respond.

    I’m open to criticism of the actual post I wrote, because I think reasonable people could certainly disagree with it. You’re a smart person, and I value your opinion. I feel a little blindsided, actually.

    That said, I always feel like it’s unwise to immediately blame the reader or play the victim when blogging. Miscommunication would be my fault first. So I apologize if I didn’t make the scope of my thoughts quite clear enough, and left you with the impression that I was either arguing for A) some sort of RMS-idealized prioritization of openness or B) that everyone should be a programmer. That wasn’t my goal at all.

  2. peterb says:

    Jane, you ignorant…!

    (I’m kidding. I’M KIDDING).

    Duplicating effort, as you say: perhaps I’m just overly touchy about this topic, but the particular paragraph in your post that motivated me to reply was:

    It’s hopelessly reductionist, of course, to say that consoles cause the digital divide, or that they’re even a major causal factor compared to problems of poverty, lack of role models, and education. But I think it’s hard to argue that the console model–locked-down, walled-garden systems running single-purpose code–doesn’t contribute to the problem. And it’s worrisome that the big new computing paradigm (mobile) seems determined to follow the console path.

    I assumed, from your article, that that was your worry, not Latoya’s. If I’m misunderstanding, please let me know. I guess I don’t see why it’s worrisome at all, and my article is an attempt to articulate why I feel strongly about that. I see technology as enabling people to do things they couldn’t do before. I frequently read and hear statements people who don’t actually care about the end user suggesting that tinkering should be prioritized over actually enabling the customer (see: Cory Doctorow). I feel that that attitude is reactionary, elitist, and harmful, and it makes me react strongly.

    I apologize if I came off as overly strident. I also apologize for comparing you to Cory Doctorow. I wouldn’t wish that on anyone.

  3. Thomas says:

    I’ll leave the substantive response on M0. I’ll just say that I think it’s funny that in our simultaneous responses on our respective sites, when we both went looking for an example of FSF extremism, we both landed on Cory Doctorow.

  4. psu says:

    I think we can all agree that Cory Doctorow is a self-centered moron.