Ten Technical Communication Myths

Geoff Hart rips apart the myths in technial writing. Great post.

Improving technical documentation

Technical writers all over the world are debating on how new approaches and processes can dramatically improve the quality of the documentation produced.

A few suggest that Usability testing, even with limited resources, can add value to the documentation you produce. Other suggest moving documentation to the Web 2.0 model for ease of use and adopting agile documentation. There are people who cite Google's example of comic documentation when they released their new browser, the Chrome.

Daniel Brolund suggests User Guide driven documentation where a snippet of the user guide describing a new feature is prepared. This is an interesting idea in that the techncial writers get a chance to become involved in the documentation process at the initial stages of software development itself. Click here to read Daniel's post.

Comics as technical writing

Google while unleashing its new browser Chrome, has created another great stuff. It's a comic book about the browse.

Check it out at http://blogoscoped.com/google-chrome/2