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
Scientific writing What Mick Southern taught me was both the imperative to and the means of writing scientific prose—“if it’s not published it’s not done,” as a later adviser put it. Mock showed me that the rather dry technical requirements of scientific writing did not necessarily mean that elegance, humor, and even wit need be excluded from the scientists’ products. Roger Kitching, A Reflection of the Truth Selling new ideasYou cannot consume what is not produced sciencewriting