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
Translation is always a treason Translation is always a treason, and as a Ming author observes, can at its best be only the reverse side of a brocade—all the threads are there, but not the subtlety of color or design. But, after all, what great doctrine is there which is easy to expound? The ancient sages never put their teachings in systematic form. They spoke in paradoxes, for they were afraid of uttering half-truths. They began by talking like fools and ended by making their hearers wise. Lau Tzu himself, with his quaint humor, says, "If people of inferior intelligence hear of the Tao, they laugh immensely. It would not be the Tao unless they laughed at it." Okakura Kakuzō, The Book of Tea The work is what it means zen