#27601
Why do we bother with models or documentation? They don't execute, and our customers pay us for working code, not pretty pictures. We bother with models to communicate. The idea is that a graphical object model can show how objects fit together more clearly than looking at the source, an interaction diagram can show a collaboration better than figuring out the call path from several class definitions. But so often the design documentation fails in this, and leaves me puzzled on my sofa.
Fowler, Martin. MartinFowler.com (1997). Articles>Documentation>Agile>Extreme Documentation
#24885
Enhancing Our Image: Creating Good Public Relations 
Effective chapter public relations results in an increase in membership, more interested and active members, and an awareness of technical communication as a valid and an important profession. This workshop teaches general public relation skills, such as how to write effective press releases, how to get your chapter events treated as news, and how to create and then maintain a press list.
Braz, Lisa M., Susan L. Fowler, Alan Korwin, and Nancy Martin. STC Proceedings (1994). Articles>TC>Marketing>Press Releases
#32171
If you document everything, you are giving everything an equal weight. Do that for a complex system, and you are buried in detail. In any system there are some aspects that are more important than the others, key aspects of the system that once understood, will help someone to learn more. The art in documentation is to find how to document these aspects as clearly as possible. In this you emphasize these areas, and leave the details for the code.
Fowler, Martin. Distributed Computing (1997). Articles>Documentation>User Centered Design>Minimalism
