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
Rain Chains & Musical Drains Show image 0 Show image 1 Show image 2 A rain chain in winter; Dresden Kunsthof Passage; Drainage planters near Pike Place Market in Seattle. If there is a larger takeaway here perhaps it is about paths of least resistance, with regards to both the actual flow of water and design decisions. On the one hand, it is easy to blindly follow regional precedents and traditions with long histories (or grab whatever is handy at the hardware store). On the other hand, sometimes it makes sense to take a step back and decide consciously how to reveal (or conceal) a natural process. Roman Mars & Kurt Kohlstedt, 99% Invisible 99percentinvisible.org Rain chains waterarchitecturedetailspatterns