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
Men are not an abstraction Placing work and commerce near residences, but buffering it off, in the tradition set by Garden City theory, is fully as matriarchal an arrangement as if the residences were miles away from work and from men. Men are not an abstraction. They are either around, in person, or they are not. Working places and commerce must be mingled right in with residences if men, like the men who work on or near Hudson Street, for example, are to be around city children in daily life—men who are part of normal daily life, as opposed to men who put in an occasional playground appearance while they substitute for women or imitate the occupations of women. Jane Jacobs, The Death and Life of Great American Cities 9. Scattered Work genderwork