Atlas · Details
Return of the Mystery Machine Bus
Author’s note
This essay was almost lost to time. I had completely forgotten about writing it, and it disappeared with Google+. I stumbled on a draft accidentally in Google Docs while making this site, and we found the gist and resurrected it. Fifteen years later and I think it's a great read, with some punchy jokes and a few surprising insights.
AI Notes
The sequel to Notes from the Mystery Machine Bus, posted to Google+ on 15 August 2012, two and a half weeks after the original. Like its parent, the only durable public copy was a GitHub gist preserved by an audience member (taylor/3804760); the underlying Google+ post vanished when the platform shut down. The argument extends in three substantial directions: the conservative-vs-liberal divide is reframed as a difference in how programmers regard their code (asset vs. liability); the planning style is recast as a choice between building cities and building military encampments; and the deep technical disagreement is located in action at a distance — the question of whether other people are allowed to reach into your code and change how it behaves.
The first half is reactive — responding to commenters on the original Bus piece, defending the political-axis taxonomy against false-dichotomy objections, and refining the model from "liberal-vs-conservative" toward something closer to "libertarian-vs-conservative". The second half, beginning with "Do You Respect Your Code?", is where the new material lives. The anecdote about Gregor Kiczales presenting AOP at Amazon — "Because sometimes code is Broken, and this gives your users a way to fix it without bothering you" / "But Sir, you are mistaken. Our code is Awesome" — is one of the cleanest worked examples in the corpus of the liberal/conservative divide playing out as a technical disagreement inside an engineering organization.
Related listings
-
2012
Notes from the Mystery Machine Bus
The essay this one is a sequel to — the original liberal/conservative software-engineering taxonomy. Read that one first; this one extends and answers.
-
2007
Code's Worst Enemy
Referenced by name in the 'Do You Respect Your Code?' section. The earlier argument that code size is the single most serious problem in software — the position the liberal half of this essay is built on.
-
2004
Is Weak Typing Strong Enough?
Referenced by name; the Perl-vs-Java showdown that Steve points back to as evidence for the liberal view on language choice.