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
Two Hundred Fifty Things an Architect Should Know An Essay by Michael Sorkin www.readingdesign.org The distance of a whisper.CornersWant, need, affordWhat the brick really wants.Borders+3 More 136 things every web developer should know before they burn out and turn to landscape painting or nude modelling architecturedesigncollections
Want, need, afford What the client wants. What the client thinks it wants. What the client needs. What the client can afford. What the planet can afford. ux
What the brick really wants. The material finds the right objectWe are working against the grain of the woodThe joy of the humble brick material
Logjam That there is a big danger in working in a single medium. The logjam you don’t even know you’re stuck in will be broken by a shift in representation. creativitymedia