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
v0.crap I couldn’t seem to convince my writers that I was genuinely ok working with a super rough first draft — i.e., that I’d harbor no hidden judgment about their intelligence, commitment, or excellence at their craft. So I came up with a new word. “Just give me a v0.crap.” (Pronounced “version zero dot crap”.) v.0.crap works because it’s attuned to the psychology of the situation. It’s punching through our innate desire not to “look bad”, plus years of corporate conditioning that tells us not to share less-than-polished work. It’s easier for people used to delivering exceptional work to feel they’ve exceeded the goal of “crap”; they can sit comfortably in “good enough for the current purpose.” Courtney Hohne, The monkey, the tiger beetle and the language of innovation blog.x.company Writing, Briefly qualityideaswritingmaking