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
From the desk of: Austin Kleon How do you work? When I get home, I have two desks in my office — one’s “analog” and one’s “digital.” The analog desk has nothing but markers, pens, pencils, paper, and newspaper. Nothing electronic is allowed on the desk — this is how I keep myself off Twitter, etc. This is where most of my work is born. The digital desk has my laptop, my monitor, my scanner, my Wacom tablet, and a MIDI keyboard controller for if I want to record any music. (Like a lot of writers, I’m a wannabe musician.) This is where I edit, publish, etc. Austin Kleon & Kate Donnelly, From the desk of fromyourdesks.com Forget the computer — here’s why you should write and design by hand drawingwork