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
Fucking up the world City Hall by Rafael Moneo, Logroño, La Rioja, Spain. Alexander : At least my experience tells me, that when a group of different people set out to try and find out what is harmonious, what feels most comfortable in such and such a situation, their opinions about it will tend to converge, if they are mocking up full-scale, real stuff. Of course, if they're making sketches or throwing out ideas, they won't agree. But if you start making the real thing, one tends to reach agreement. My only concern is to produce that kind of harmony. The thing that strikes me about your friend's building – if I understood you correctly – is that somehow in some intentional way it is not harmonious. That is, Moneo intentionally wants to produce an effect of disharmony. Maybe even of incongruity. Eisenman: That is correct. Eisenman: I find that incomprehensible. I find it very irresponsible. I find it nutty. I feel sorry for the man. I also feel incredibly angry because he is fucking up the world. Christopher Alexander & Peter Eisenman, Contrasting Concepts of Harmony in Architecture Forces of conflict beauty