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
What the prototype tells you A Fragment by Matt Webb interconnected.org As soon as I make something, I think of the 100 things I want to have next. That’s why prototyping is good. You don’t need to have much imagination, you just listen to what the prototype tells you. The situation talks backCo-Evolution of Problem and Solution Spaces in Creative DesignThe Battle for the Life and Beauty of the EarthThe game discovering itself designmaking