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
e-worm.club A Website by Zach Sherman e-worm.club I’m building a custom pleroma client so that my friends and I can have a cute, self-hosted social network to post about politics and art. Besides being much more visually interesting than our facebook messenger groupchat, e-worm also attempts to solve design problems around conversational, collaborative thinking. The biggest of these problems is the inherent ephemerality of our groupchat— it doesn’t really succeed as a collaborative thinking space because it has no long-term memory. When messages are constantly buried under new ones, it places the burden on us to remember previous conversations. So the ultimate design goal for e-worm is to create a self-archiving conversational interface that preserves thought and helps us keep thinking new things rather than going in intellectual circles. micrositescommunicationthinking