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
When I was 22 A Quote by Nicholas Ashe Bateman nofilmschool.com What's really challenging for me working on something on an idea level for close to 8 years, it's really hard to not look at yourself. The decision-making process includes a conversation with myself: sometimes I'm going to side with 2015 version of Nick, sometimes the 2017 Nick isn't the right guy for this, etc... So much of the process of making the movie has changed the movie. I really just tried to make the movie I wanted to make when I was 22. When I serviced that, it worked really well. The idea grows as they workThe Wanting Mare makingidentity