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
Don't Write the Tedious Thing An Article by Maud Newton maudnewton.medium.com Ugh, now I have to write this boring part, I would think. I would spend a few days in active rebellion against this directive that I imagined the book was imposing. Then I would realize: this is my book! There are no rules! I can write it however I want! Also, I would think, if I’m bored by something that I believe I need to write, the reader undoubtedly will be too, if not because the subject is inherently boring, then because I myself find it so unbearably tedious to imagine discussing it for five pages. Often as not, I would remember some aspect of the subject that deeply interested me, something a little outside the way it’s usually perceived or written about. Then I would meditate on that, and soon I would be scribbling notes from an increasingly excited place until I found a way forward. A form of beginner’s mind. Zen Mind, Beginner's Mind boredomwritinginterest