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
Tokenize This An Artwork by Benjamin Grosser bengrosser.com Different from the typical website whose URLs act as persistent indexes to a page and its contents, Tokenize This destroys each work right after its creation. While the unique digital object remains viewable by the original visitor for as long as they leave their browser tab open, any subsequent attempt to copy, share, or view that URL in another tab, browser, or system, leads to a “404 Not Found” error. In other words, Tokenize This generates countless digital artifacts that can only be viewed or accessed once. wwwarteconomics