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
Craft and Material in Digital Design An Article A little bit more about the stoneIt is how we come to understand our medium craftmaterialsoftware
A little bit more about the stone In the documentary Rivers and Tides, artist Andy Goldsworthy repeatedly struggles to stack stones into a sculptural cairn. Over and over the stones fall. Each time, Andy’s sculpture stands a little taller before the moment of failure. At a penultimate moment in the episode, the ever-patient Goldsworthy begins to look exasperated. He’s just staring at the rocks scattered on the ground, studying them intently. A curious passerby has watched him fail a few times, and Andy tells the man, “Every time, I learn a little bit more about the stone. I’m learning how it works.”
It is how we come to understand our medium There is such a unique quality to experiential learning, through direct experience with a material. It cannot be substituted through lectures or books. It must be felt. It must be earned through time well spent, through making and failing and re-making. It is how we come to understand our medium. If you’re a digital designer who doesn’t understand basic principles of computer science, or has never written a bit of code, or has never built a website, what are you doing? What can you say about the material you shape? The idea that designers in the information age shouldn’t waste their time with this skill baffles me. It is woefully misguided advice. A digital designer who has not learned the nature of their medium is a designer unprepared to argue for their vision. This is a designer who is unable to push back against the criticism of skeptical engineers. This is a designer who risks offering opinions instead of solutions. If you are crafting experiences in the digital space, you should know what’s required to implement your ideas. You should try implementing it yourself, (if only to build empathy with your developers!)