There are 30 posts tagged technical writing (this is page 3 of 3).
Technical writing is often an unspoken, and sometimes unheard of, process across business and technology sectors. Many leading R&D centers are bursting with bright spark engineers, sharp-minded designers, and idea generators who make products and services come to life. However, this doesn’t mean that they can explain their product or service accurately or concisely.
Simply put, technical writers produce documentation to help the average reader understand how to use products or services. Few in our field attain fame for their writing, and those who do – like Ted Chiang, Kurt Vonnegut, and Amy Tan – are generally known for their non-technical work. Find out more about technical writing.
Technical writing differs from other forms of writing. Its aim is generally to provide instruction about a subject to help users solve problems. Because technical writing has such a unique, defined goal, good technical writing adheres to specific guidelines. Here we look at some of the most important things to avoid when writing technical documents.
It’s official: the Term Master of 2010 is ready to be announced to the world. Stop on by for an exclusive interview with the translator who entered more than 10,000 terms and translations into TermWiki.com, securing her position as a linguistic expert and the proud new owner of a Samsung Galaxy Pad. Stop on by and check out her story!
For those of you who didn’t have the opportunity to attend, the DITA Europe 2010 Conference in Vienna was a rousing success. In this guest entry, Carl Yao, the Vice President of Global Strategy at CSOFT, relates two DITA success stories from companies that saved a ton of money on translation and localization as a direct result of applying XML-based DITA standards to their content development processes. Carl also gives a quick rundown of his own presentation at the conference, “How to Become an Expert Terminologist in 30 Minutes.” Come check it out!
