Document Development

by Geoff Hart

While prospecting for information on a Web site that I visit fairly regularly, I recently fell victim to a fascinating Web page trick. The trick took advantage of the kind of reflexive ("programmed") response we each develop once we grow so familiar with a task that we no longer consciously think about what we're doing.

by Sean Hower

As a technical writer, you likely work with a myriad of different files for each project you work on; a single document or document set can often be derived from dozens if not hundreds of source files, potentially created by dozens of people over a period of time. Couple that with working on multiple projects, managing document revisions, and last-minute document changes, and you likely face a challenge in just accessing and managing the files you need.

by Liz Russell

If you're a writer like me, news of a fresh assignment brings both excitement and anxiety. New assignments offer opportunities to further our knowledge and expand our portfolios, and they may result in a bonus or a more lucrative contract. But new projects can also inspire angst and dread if you have past experience with projects that involved false starts, unrestrained scope creep, misunderstandings between team members, uncommunicative teammates, or unfamiliar technologies.