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
Upstream, Downstream To truly increase innovation, I think we need policies focused on what goes on even further upstream, before much of the supply of new inventors is inevitably siphoned off into distractions, dead ends, and failure. Most policies inevitably have a marginal effect, but a slight expansion of the incoming swell of potential inventors can have a much greater impact than fiddling with the incentives of the few hundred who’ve already somewhat made it to the final trickle. Increase the strength of the flow upstream, and everything downstream flows the faster too. Anton Howes, Age of Invention antonhowes.substack.com Who Becomes an Inventor in America? The Importance of Exposure to Innovation innovation