Technical Writing, a form of technical communication, is a style of formal writing and business communication, used in fields as diverse as computer hardware and software, chemistry, the aerospace industry, robotics, finance, consumer electronics, and biotechnology. Good technical writing clarifies technical jargon; that is, it presents useful information that is clear and easy to understand for the intended audience.
#30766
Is Your Website Poised to Deal With Its Growth? 
Every webmaster nourishes the dream that his or her website will make it the big way. This is very much human because people carry out any task in ardent hope. What is more human out here is that earthy fellows like us base our aspirations more on speculation rather than specific set of steps undertaken to bring the dream a bit closer to reality. And this is not all, particularly in case of growth of a site which brings newer problems in the wake of its growth. It cannot be disputed that you can probably get some good web hosting on economy price. But if you expect top of the line service on this price, acknowedge gracefully that your are just asking for the moon. Probably you are not catching up with wisdom that business needs decisive investments.
Azam, Rahbre. Amateur Writerz (2008). Articles>Documentation>Web Design>Technical Writing
#13920
The Issue of Quality in Professional Documentation: How Can Academia Make More of a Difference? 
This article recommends strategies academics can use to contribute to an issue of great interest in industry: how best to define, measure, and achieve quality documentation. These strategies include contextualizing quality definitions, advocating the use of multiple quality measures, conducting research to identify specific heuristics for defining and measuring quality in particular workplace contexts, and partnering with industry to educate upper management about those heuristics and the benefits of promoting technical communicators to the strategic role of organizational “gatekeepers of quality.”
Spilka, Rachel. Technical Communication Quarterly (2000). Articles>Documentation>Collaboration>Technical Writing
#22163
Issues in Professional and Technical Writing
In this course you will learn the methodology of single sourcing and the technology of a help applications tool (RoboHelp Office X4).
McShane, Becky Jo. Weber State University (2004). Academic>Courses>Writing>Technical Writing
#26474
Now it is very important to recognize the vital role of a technical writer and services expected to provide to justify the requirements of this profession. Since technical writer is a sub category of technical communication, that involves other categories involved in documentation, like content writer, software configuration manager, technical editor, information designer and many more.
Albing, Bill. KeyContent.org (2005). Articles>TC>Communication>Technical Writing
#23716
It's a Marathon, not a Sprint: Managing Your Technical Writing Career
I've trained for and run three marathons. My marathon experiences taught me lessons that can be applied to going the distance in a technical communication career. Going the distance requires a willingness to “get going,” continually work on the basics, cross- train, avoid being distracted by what was and what could be, and learn from experience.
Harvey, Michael. STC Proceedings (2003). Careers>Advice>Writing>Technical Writing
#31794
It's Not the Tool, It's the Writer
This blog post ponders whether or not technical communicators are sometimes too enamoured with the tools, and because of that lose sight of what's best for the reader.
DMN Communications (2008). Articles>TC>Technical Writing>Technology
#22611
Job Futures for Authors and Writers (including Technical Writers)
A discussion of career prospects in writing, including technical writing.
Human Resources Development Canada (2003). Careers>Writing>Technical Writing>Canada
#21663
Jobs for Writers: Technical Writing and Business Communications Jobs 
A specialist job opportunity newsletter for writers, copywriters, editors and content developers.
#22792
Offers advice on creating effective FAQ documents.
Hart, Geoffrey J.S. Intercom (2004). Articles>Documentation>Technical Writing>FAQ
#29360
A blog about technical writing, information architecture, topic authoring, social media, and other technologies that catch Anne Gentle's eye.
Gentle, Anne. Just Write Click. Resources>Writing>Technical Writing>Blogs
#24851
Kelly's Laws of Technical Writing (retro version)
A reaction to the dysfunction of technical writing in the modern workplace.
Kelly, William T. Typepad.com (2004). Humor>Writing>Technical Writing
#19739
The Keys to Clarity, Consistency, and Correctness
How can you make documentation more clear, consistent, and correct for your users? Following are some guidelines I find effective when documenting concepts and organizing documents.
Hassell-Corbiell, Rives. Indus (2002). Articles>Documentation>Writing>Technical Writing
#20777
The top 16 things likely to be overheard if you had Klingon technical writers working on your documentation team.
Documentia (2003). Humor>Writing>Technical Writing
#26825
KnowGenesis Online Forum for Technical Communication
KnowGenesis is a forum to promote free exchange of thoughts, knowledge and literature in the field of technical communication. KnowGenesis is the dream shared by two technical communicators - Ginu George and Saurabh Kudesia. Their intense interest clubbed with knowledge collaboration led to the formation of KnowGenesis. The co-foundersí ideology is reflected in the way KnowGenesis is designed. KnowGenesis provides open access to all its content on the principle that making information freely available to the public supports a greater global exchange of knowledge.
Kudesia, Saurabh. International Journal for Technical Communication. Resources>Documentation>Online>Technical Writing
#26780
KnowGenesis Online Library for Technical Communication
KnowGenesis Library is India's first online library for Technical Communication. Within few months of its launch, KnowGenesis library is already creating waves in the international technical writing community. The library has more than 1200 important documents, reference materials, articles, e-books etc contributed by our members. KnowGenesis library is also partnering with Digital Curation Center UK for promoting digital preservation and is opening great opportunities for Indian technical writer to mark their presence in the international market. The information provided on the KnowGenesis library is FREE for all and just require a one time FREE registration (http://knowgenesis.org/tc/index.php?option=com_registration&task=register). There is no charge/fee whatsoever involved for using the library material. Registered users can submit their work to the library, browse through the large collection of material and can even volunteer for the administration.
Kudesia, Saurabh. International Journal for Technical Communication (2005). Resources>Documentation>Tools>Technical Writing
#29266
A weblog about technical documentation, training, and marketing materials.
Campbell, Caren Weiner and Barry Campbell. Knowledge Work. Resources>TC>Technical Writing>Blogs
#28827
Review: Law and Internet Cultures
Kathy Bowrey's Law and Internet Cultures critically deconstructs the law in the context of legal culture, and especially looks at how U.S. law, practice, and culture has influenced technology law. Bowrey, a lecturer in the Faculty of Law at the University of New South Wales, writes as an "Australian author" but her analysis clearly contains a global perspective as she looks to global structures and laws in other countries such as the United States. The book's analysis draws upon an incredibly broad range of literature including but not limited to traditional "literature" (e.g., Orwell's 1984), economic analysis, communications theory, and cultural studies. She stretches her analysis, connecting the heretofore disconnected (like Foucault, Coombe, Mandeville's travels, Napster, Grokster, etc.) and makes these horizontal connections in the context of discussions of verticality--like globalization, international standards, international patent norms, and global governance. The reading will be difficult for folks without a solid background in information technologies and law (and is just plain difficult for reasons mentioned below), but Bowrey does provide at least brief definitions and description of acronyms where need be. She tends to begin chapters with details and then brings things together at chapter's end--but this strategy seems to work for the complex subject matter. This is a great book for reading out of order or skipping to particularly relevant sections. Each section of each chapter can hold together on its own. Numerous diagrams and illustrations add to the flavor of this unique and much-needed book.
Rife, Martine Courant. H-Net (2006). Articles>Reviews>Legal>Technical Writing
#20500
A technical writer...hey aren't those like the guys who wrote the manual for the Quantum Leap Accelerator?
Tipple, Mark. InFrame. Humor>Writing>Technology>Technical Writing
#22598
Learn to Read Technical Writing!
Why is my daughter not being taught to read technical literature? Practical things like reading a VCR manual or a pamphlet on health.
Kamath, Gurudutt R. IT People (2003). Articles>TC>Writing>Technical Writing
#22690
Learning the Fine Art of Reviewing
If you asked me what the most painful part of being a technical writer is, my answer would be: 'Getting reviews on time. Getting good feedback and inputs on your work.' For me technical writing has been very pleasurable because I hardly got any review comments. My morale has therefore been very high. Project managers, developers and others are so busy trying to come up with good software (read trying to fix all the goof-ups and bugs!) that they usually tend to give documentation lesser importance. User manuals, who reads them anyway? We do not have time for it!
Kamath, Gurudutt R. IT People (2003). Articles>Editing>Collaboration>Technical Writing
#21549
Legal Communication in Technical Communication Programs: Worth Thinking About?
What, if anything, should technical communication programs teach their students about the nature of law and the production of legal discourse? When is technical writing also legal writing, and vice versa; when is legal writing (really) technical? Are there distinctions worth maintaining and dissolving here? Do lawyers' relationships to, and problems with, legal writing contexts and processes parallel in important ways technical writers' relationships to, and problems with, technical writing contexts and processes? If they do, is a conversation between the disciplines worth institutionalizing, at least experimentally, in each other's programs?
Stratman, James F. CPTSC Proceedings (2001). Articles>Business Communication>Legal>Technical Writing
#22157
Leveraging Complex Content for the Support Chain
The support chain is becoming increasingly important as we begin to understand the deep underlying economic trends of the last half-century.
Osnat, Rani. ComTech Services (2001). Articles>Content Management>Technical Writing
#31728
'Lone writers' — those people who work as their employer’s only staff writers — are a different breed, with their own unique set of professional and personal challenges. At the same time a blessing and a curse, the lone writer life offers flexibility, variety, and autonomy, along with feelings of stress, isolation, and burnout.
Potsus, Whitney Beth. Writing Assistance (2006). Careers>TC>Technical Writing
#23391
With his back towards the reader, a bucket over his head, hands and feet tied up by SGML, CALS and company standards, and half choked by all the possibilities of the latest computer system the writer tries to produce manuals and instruction books for unsuspecting readers!
Forsslund, Lars. TC-FORUM (1998). Articles>Documentation>Writing>Technical Writing
#24073
Some website that might be of interest for technical writers.
Tech Writing Jobs. Resources>Directories>Writing>Technical Writing
