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
Infinite varieties of contexts Over the course of 10 years of using Are.na, I have fully adopted the view that any piece of information can be important to a person given the right context. And on Are.na, pieces of information can be arranged in infinite varieties of contexts – their respective meaning shifts as the proximate information shifts. In other words, the more connections a block has, the more opportunities it has to be a nodal point. Charles Broskoski, On Motivation Seeing Is Forgetting the Name of the Thing One Sees informationconnection