TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Brecht, I believe, talked about the simple that is hard to make. One would
assume, I thought, that technical writing was harder and more exacting than
programming. It takes more training to be a competent technical writer
than to be a good programmer. We study language from the time we are
born--even before. Is there even a Ph.D. in programming? What is the
evidence of a badly written program? I would guess, from my experience
documenting programs, that they are no better than they have to be, and
neither is a lot of technical writing. I would like to set the qualities of
good programming against the qualities of good technical writing to see
which simple is harder to make.
