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
We want you to work with an artist Normally after the design was built, you would find places for the art to be located and then you would go out and select the artist that you wanted. That is historically, the traditional way to go. But this time, someone else was calling the shots. A planning official, basically, who comes along and says, “We want you guys to work with an artist.” And the architects are like, “Sure of course.” But then the official goes—“No, you don’t quite understand. We want you to use an artist as a co-equal member of the design team.” That is, the artists are going to have just as much control as the architects. It was really unheard of. Some Other Sign that People Do Not Totally Regret Life 99percentinvisible.org It passes by the river artcollaboration