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
This language without words There must be a language that doesn't depend on words, the boy thought. I've already had that experience with my sheep, and now it's happening with people. He was learning a lot of new things. Some of them were things that he had already experienced, and weren't really new, but that he had never perceived before. And he hadn't perceived them because he had become accustomed to them. He realized: If I can learn to understand the language without words, I can learn to understand the world. Paulo Coelho, The Alchemist The quality without a name language