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.
Taking notes has always helped me zero in on the interesting questions.
In taking field notes, the way to find these peculiarities is to keep track of as many observations that may not appear at the time to be relevant at all.
I’ve been keeping journals of one sort or another since I was a teenager, and if there is one thing I can now confidently say about all this scribbling and note-taking, it is that if it wasn’t written down, it didn’t happen. The more I wrote the more that did happen, because all this process stirs up ideas. Stopping to sit and write costs time and energy, and some biologists feel that it should be discouraged.
Note-taking helped transform me from a young boy on barefoot runs who passively observed the tangled bank of the Maine woods into a naturalist-scientist who is an active participant in unraveling the mysteries of the natural world.