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
I can only conceive for you I cannot perceive for you. I can conceive for you and we can then in a sense hold a general agreement about quality of conception and we may all operate under it and that's what is known as a common agreement. But the area of perceiving as such is totally individual, there's no way that we carry it in that sense. This is not an antisocial gesture; it is in fact a highly ethical one, since trying to get another person to see what and how you see has the potential to become a violation of the other's own autonomy: There is nothing more unethical than having ambitions for someone else's mind. Robert Irwin, Robert Irwin: A Conditional Art Ambitions for someone else's mind