Designer, implementor, user, writer A Fragment by Donald Knuth dl.acm.org Thus, I came to the conclusion that the designer of a new system must not only be the implementor and the first large-scale user; the designer should also write the first user manual. The separation of any of these four components would have hurt TeX significantly. If I had not participated fully in all these activities, literally hundreds of improvements would never have been made, because I would never have thought of them or perceived why they were important. Eating your own dog food making
I don’t believe in Zoom fatigue An Article by Matt Webb interconnected.org It’s not Zoom fatigue, it’s Zoom whiplash. It’s a hunch. I can’t prove this. The trick to get around this is to move smoothly up and down the gradient of social interaction intensity, never dropping below a basic floor of presence: the sense that there are other people in the same place as you. Instead of having two modes, “in a call” and “on my own,” we need to think about multiple ways of being together which, minimally, could be: In a video call In an anteroom to a video call, hearing the sound of others In a doc together On my desktop but with the sense that colleagues are around And the job of the designer is to ensure that their software ensures the existence of these different contexts, instead of having the binary on-a-call/not-on-a-call, and to design the transitions between them. communicationworktransitionssoftware