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
What the painting was not about That is why for many years Irwin declined to allow his work to be photographed, because the image of the canvas was precisely what the painting was not about. Indeed, the problem is even more complicated than that. For in a very real sense the achievement of these paintings was in their making, and the finished canvas at one level is only an incidental relic, a fossil of that original process of discovery: not only do you have to be present before these paintings in order to experience them, it may be that you have to have made them as well. Lawrence Wechler & Robert Irwin, Seeing Is Forgetting the Name of the Thing One Sees Only a mind opened to the quality of things photographyimages