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
Babble and Prune For those who read and listen much more than they speak (guilty), an overly-strict Prune filter is applied to their writing; when these people go to write something of their own, their minds don’t produce thoughts nearly as “coherent, witty or wise as their hyper-developed Prune filter is used to processing”. Hence, my dilemma and an opportunity to break out of this trap. I recognised that if I attempted to write at the quality I was used to reading at, first time every time, my brain would promptly grind to a halt—like trying to brainstorm with a group that laughs at your suggestions. writingcreativity