Background textures of work An Article by Lucy Keer lucykeer.com One thing I've been enjoying about working as a technical writer is that the minute-by-minute texture of the work feels right. Something about formatting text, faffing about with SVGs, trying to rewrite a sentence more clearly... it's just enjoyable in itself, and I feel at home with it. ...Working as a programmer was very much not like that. There's something in the rough vicinity of professional dev work that I do like, which I could probably label as 'iterative hobbyist tinkering with websites'. I like working on something with a strong visual component, and I like to be inside of a fast feedback loop, and I'm mostly interested in just somehow bodging through until it works. I'm not very interested in either the computer-sciencey side of programming — data structures, algorithms — or the software-engineerey side of making things run reliably at scale in a maintainable way. So maybe it's not surprising that the minute-by-minute texture of professional programming was just... kind of bad. Occasional fun bits when I got into something, but the background experience was not fun. workproductivitymaking
The reflective craftsman Specialized tools like bench shears have proliferated throughout history in part because craftsmen necessarily do the same task with the same tool over and over. After a while, the task becomes routine, and the craftsman is able to perform it with predictable skill. The most creative of artisans is frequently one who, in the midst of routine, pays attention to the details of the work and the tools that effect that work, and so it is that the reflective craftsman develops ideas for new and improved tools in the course of working with those that he perceives to limit his achievement or efficiency. Henry Petroski, The Evolution of Useful Things Eating your own dog food toolsroutineskill