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
Do they really need it? Does Google really need playful doodles to deliver the value they consistently provide in search results? Does Stripe really need to spend so much energy on the design of its site and SDK’s, which after all, are primarily for the developers that use their API’s? Does Apple really need to sweat the literally thousands of very subtle and often not consciously noticed interactions on its devices? Marty Cagan, Ensuring Excellence On Taste