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
Don't get me wrong An Article by Austin Kleon austinkleon.com No phrase makes me want to stop reading more. “Don’t get me wrong” is usually a tell — a kind of backpedaling that sets off an internal alarm and suggests I’m a) reading a hyperbolic argument (which, admittedly, describes the majority of online writing these days) or b) that the writer is just lazy. Either way, when I see “don’t get me wrong,” I start to suspect I’m reading a piece of writing that might not be worth my time. If you find yourself using “don’t get me wrong,” I have a suggestion: Delete the phrase and rewrite what came before it so I don’t get you wrong. writing