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
Input as collage An Article by Austin Kleon austinkleon.com Your output depends on your input, but a lot of your input is random: you’re interested in lots of different things, and those things, occasionally, will talk to each other in your work. Lately I’ve been thinking about being more intentional with input. Thinking about input as collage. Taking the principle of juxtaposition (1+1=3) and using that to guide your input: what weird, seemingly disparate things can you feed your brain that will come out later in a new mix? The input collage can be subject or genre based and even better if it’s multi-media. ...There’s a balance here between feeding your brain intentionally and then backing off and letting your brain do the subconscious work of mixing your inputs together. creativityintent