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
It passes by the river "Artists need to be in there from the start, making the argument for quality. The key to this thing is, for example, if you give an engineer a set of criteria which does not include a quality quotient, as it were—that is, if this sense of the quality, the character of the place, is not a part of his original motivation—he will then basically put the road straight down the middle. He has no reason to curve it. But if I can convince him that quality is absolutely a worthwhile thing and we can work out a way in which the road can be efficient and also wander down by the river, then we essentially have both: he provides his sort of expertise in that the road works, I provide quality in that it passes by the river. In that way, art gets built into the criteria from the beginning rather than being added on afterward." Lawrence Wechler & Robert Irwin, Seeing Is Forgetting the Name of the Thing One Sees We want you to work with an artistThe problem with ornament qualitydesignfunctioncollaboration