Software Engineering as a Craft An Article by Thomas Wilson thomaswilson.xyz 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. craftsoftware
All the way through "There's a consistency to physical objects that somehow reads all the way through, so that when you make a physical object, if it lacks the proper amount of weight or if it lacks a certain density...I mean, if its outside says, 'I weigh so much and I have such-and-such a density,' and when you pick it up, you discover an inconsistency there, then you can sense that, you can see it, even without picking it up. It's absolutely essential that everything be done all the way through." Lawrence Wechler & Robert Irwin, Seeing Is Forgetting the Name of the Thing One Sees Invisible substanceA great painting has to be better than it has to beFinished on the insideSigning partyWhy YKK zippers are the brown M&Ms of product designYou'll know it's there objectscraft