Alan Jacobs
revisiting architectural blogging
Makers and Making
An Article by Alan JacobsThe [Silmarils] are good; their making was at least potentially innocent; but afterward arose a lust for owning and controlling that led to great tragedy… The aspect of humanity which the elves represent most fully – both for good and ill – is the creative one.”
And this is why “making” in and of itself is not the answer to our decadent moment. “Love of things, especially artificial things, could be seen as the besetting sin of modern civilisation, and in a way a new one, not quite Avarice and not quite Pride, but somehow attached to both” – and this is the Fëanor Temptation. It is in light of this temptation that I advocate repair, which is a mode of caring for what we have not made, but rather what we have inherited. We will not be saved by the making of artifacts — or from the repair of them, either; but the imperative of repair has these salutary effects: it reminds us of our debt to those who came before us and of the fragility of human constructs.
Against Canvas
An Article by Alan JacobsEven with all the features and plugins, Canvas presumes certain ways of organizing classes that might not be universal, just typical. And if (like me) you’re an atypical user, you have to choose between constantly fighting with the system or gradually doing more and more things the way Canvas wants you to do them. This, by the way, is why it’s never true to say that technologies are neutral and what matters is how you use them: every technology without exception has affordances, certain actions that it makes easy, and other actions that it makes difficult or impossible. A technology whose affordances run contrary to your convictions can rob you of your independence — and any technology deployed on the scale of Canvas will inevitably do that. It will turn every teacher into an obedient Canvas-user. I don’t want to be an obedient Canvas-user.
But we're not there
A Fragment by Alan JacobsGet your fucking hands up
Get on out of your seats
All eyes on me, all eyes on me...But we’re not there. There’s a cheering-audience soundtrack, but it’s fake, Burnham knows it’s fake, he’s the one who put it there. He doesn’t know whether we’re watching, whether our hands are up, whether all eyes are on him.
On the "Building" of Software and Websites
I’m beginning to suspect that software, and more conspicuously the Web, is fundamentally the wrong shape for the archetype of the construction project.
You are agreeing to make a Thing
When you sign the contract for the construction project, you are agreeing to make a Thing—app, website, whatever. And you will have agreed to deliver this Thing on a certain date, also known as a deadline. From this point forward, the goals of shipping the Thing on time and actually solving the client’s problem will be in competition with each other.
The Thing-deadline calculus
Now, I understand deadlines. I understand that the plane will take off whether or not I’m on it, or the importance of beating the holiday retail rush, or that "the show must go on". It is perfectly clear to me how people use timekeeping technology to coordinate social activity. It’s actually quite remarkable when you step back and look at it. But, over the years, I have observed that there is a difference between those examples and the ones around the delivery of Things, which tend to be completely arbitrary. When you wrap an arbitrarily complex endeavor up in a neat launch date, the goal seems to be more about coercing the people beneath you to absorb the overhead of all the details you left out—that or sweating it yourself. As a tool for coordinating human activity, I have come to believe that the Thing-deadline calculus is, considering more sophisticated alternatives, unnecessarily crude.
Trees and graphs
A tree is a kind of graph, but a graph can be considerably more complex than a tree.
I have reason to believe, which for brevity’s sake I will treat elsewhere, that the most complex class of processes and structures we humans can consciously prescribe, reduces mathematically to a tree. A tree has a top, bottom, left and right. Its branches fan out from the trunk and they don’t intersect with one another. They are discrete, contiguous, identifiable objects which persist across time. Trees are Things.
Software and websites, however, reduce to arbitrarily more complex structures: they are graphs. A graph has no meaningful orientation whatsoever. No sequence, no obvious start or end—at least none that we can intuit. It is better considered not as one Thing, but as a federation of Things, like the brain or a fungus network, or perhaps a composite artifact left behind from an ongoing process, like an ant colony or human city.
Content as value
The most important consideration for any software or web excursion is content: the content of the text and other communicative media, as well as the content of the code that executes the business processes. The ability to tick off a page or piece of functionality as being done only produces a nominal successful result; the careful crafting of what one of these objects says produces a real one.