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
Staff meetings at Amazon A Quote by Jeff Bezos We have study hall at the beginning of our meetings. Staff meetings at Amazon begin with 30 minutes of silent reading. The traditional corporate meeting starts with a presentation. Somebody gets up in the front of the room and presents a PowerPoint presentation, some type of slide show. In our view you get very little information, you get bullet points. This is easy for the presenter, but difficult for the audience. And so instead, all our meetings are structured around a 6 page narrative memo. Documents vs. decks