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
Doing community There is a Japanese catchphrase, community suru, literally "making" or "doing" community. I will never forget the queasy feeling that came over me when I first heard that term, phrased as if community were a kind of event. Hold an event, bring people together, get people who might otherwise never meet to interact. It's a wonderful thought. I have nothing against events per se. However, if they are not spontaneous and voluntary, they will not last. That is my objection to the keep-it-lively concept of community. The perception of community as event stems, I think, from a yearning for the festivals and rituals that once flourished in rural communities in Japan. But those events occurred precisely because a community existed, not the other way around. Toshiharu Naka, Two Cycles Togetherness connectionurbanism