Part of the joy of working in digital policy in the UK is that many of your days start like this:
I, a Tory politician, have a brilliant plan / erudite commentary / a policy announcement on tech policy strategy. Click here to read it in this EXCLUSIVE Elite Broadsheet Newspaper piece.
We all know full well that this is how the game of politics works. These brilliant plans, erudite commentaries, and policy announcements aren’t made for you plebs. They’re made for the machine to feed the beast inside it.
The bipartisan deal contains a pot of money to repair America’s roads and bridges, and build a few more besides. This is the way we usually do infrastructure in America. First we build a ton of roads and bridges that are highly expensive to maintain, especially with our ruinously high construction costs (see this recent article by Jerusalem Demsas). Then, because costs are so high, we wait for a long time to repair the roads and bridges, until civil engineers start screeching, roads get potholed, and there’s a bridge collapse or two. Then we muster up the political will to throw the requisite shit-ton of money at the problem, the potholes and weak bridges get repaired for twice the amount it would have cost had we done it on a regular schedule and three times the amount it would cost if we were a normal rich country. And the whole cycle begins again.
The decreasingly tangible product of code, i.e. that all we have are files on a hard-drive, may make it easy to forget that writing software produces a thing. If you produce a wonky chair or an overly long fork, it’s easy to see the quality of work was not great. By calling for a perception of software as a craft, we fight against that ability to forget or not notice the final quality of the product. You could watch two software engineers with different levels of experience, or in different domains, and it wouldn’t necessarily be so easy to guess which is which, at least from a distance.
So maybe there is something to be said for the value of software as a craft, for sometimes focusing on the practice of making better, or at least different, software just for the sake of it.