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
But then the knoll was gone These banks were making the same mistake as a family I know who bought an acre in the country on which to build a house. For many years, while they lacked the money to build, they visited the site regularly and picnicked on a knoll, the site’s most attractive feature. They liked so much to visualize themselves as always there, that when they finally built they put the house on the knoll. But then the knoll was gone. Somehow they had not realized they would destroy it and lose it by supplanting it with themselves. Jane Jacobs, The Death and Life of Great American Cities 104. Site Repair