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
Narrative Strategy An Article by Tom Critchlow tomcritchlow.com An unfolding network of associations
An unfolding network of associations We know strategy is an unfolding network of associations: The evidence from the case suggests that the concept of strategy can be reappraised. From strategy as a static set of choices made at a specific point in time to strategy as an unfolding network of people, shared experiences and artifacts that is constantly being remade. And we know that only 30% of employees can articulate a company’s strategy. And I believe in the hyper-connected age we live in both of these things are becoming more true - that strategy is increasingly “in motion” and that most organizations are realizing their OODA loops are too slow for the modern world. This causes the articulation of strategy to stall and get left behind - how do you articulate something in motion? It’s easier to write strategy down when it doesn’t change right? As a result - there’s a widening gap between the perspective on strategy that the executive team has and the received ideas of the company’s direction that teams and employees have. work