A directory of resources inthe field of technical communication (and technical writing).

Technical Writing

501-524 of 1,149 found. Page 21 of 46.

About this Site | Advanced Search | Localization | Site Maps
 

« PREVIOUS PAGE 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25  NEXT PAGE »

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.

 

501.
#33531

Mike's MadCap Life

Mike Hamilton covers topics like technology, PDAs, MadCap products, technical communication and more.

Hamilton, Michael. Wordpress (2008). Resources>User Experience>Technical Writing>Blogs

502.
#34712

A Mile Wide and 30 Seconds Deep: A Metaphor for Help from Mike Hughes

Help needs to be a mile wide—it must cover everything—and 30 seconds deep—tackling only small amounts of detail at any given point.

Johnson, Tom H. I'd Rather Be Writing (2009). Articles>Documentation>Technical Writing

503.
#35634

Minimal Procedure Content: Reasoning

The procedure I wrote about creating a Twitter list uses abbreviated content. This post describes the reasoning behind and decisions made in writing the topic.

Norris, Julie. 2moroDocs (2009). Articles>Documentation>Technical Writing>Minimalism

504.
#35535

Minimizing Documentation

Is less always more? I’m not sure. But if Apple’s minimalistic designs are any indicator of trends, minimalism in documentation is something to pay attention to. Here are five ideas for minimizing documentation.

Johnson, Tom H. I'd Rather Be Writing (2009). Articles>Documentation>Technical Writing>Minimalism

505.
#23691

Minneapolis Technical Writers and Editors Directory

Web sites of technical writers and editors in the Minneapolis/St. Paul area and in nearby outstate Minnesota and Wisconsin.

Winzig Consulting Services, LLC (2004). Resources>Directories>Writing>Technical Writing

506.
#35126

The Missing Manual Authors’ Guide   (PDF)

This Authors’ Guide tells you everything you need to know to write Missing Manual. It starts out by giving you a brief introduction to the Missing Manual way of explaining things and then takes you through the nitty gritty of style guidelines, figure formatting, and so on.

Missing Manuals (2009). Articles>Documentation>Style Guides>Technical Writing

507.
#21408

Mistakes Technical Writers Make   (Word)

Inexperienced technical writers typically make a number of avoidable mistakes, including parroting the SME and hard-coding xrefs. Here is a description of some mistakes to avoid.

Docsymmetry (2003). Articles>Documentation>Technical Writing

508.
#31969

MITWA: Mentors, Indexers, Tech Writers and Associates

Whether you are an aspiring technical writer, or just starting out, or have been in the technical writing game for a while, we are here to give you the support and encouragement you may need from time-to-time.

Yahoo. Resources>Writing>Technical Writing>Community

509.
#19649

A Mixed Bag of Job Prospects for Tech Writers

One of the areas the 2001 ITAA survey looks at is supply and demand. Of the estimated 258,332 jobs that IT hiring managers predict they will add this year, only 1,799, or less than 1%, are for tech writers. This is down a whopping 91% from the year 2000 where the 20,773 available tech writer jobs accounted for almost 5% of the total. The news may not be as bad as it sounds. On the supply side, there is an expected shortfall of 1,008 qualified candidates in filling the open tech writer jobs.

Welinske, Joe. WritersUA (2001). Careers>Writing>Technical Writing

510.
#37001

Models of Professional Writing/Technical Writing Administration: Reflections of a Serial Administrator at Syracuse University   (PDF)   (peer-reviewed)

Over a thirty-year career at Syracuse University, I have been involved in setting up programs in Professional and Technical Writing (PTW) more than once, and I have also had some involvement in helping lay the groundwork for two other programs. The contexts for these various experiences differed greatly, and in all cases local circumstances and negotiation of immediate local and surrounding campus cultures had a lot to do with the outcome of such efforts. My reflections in the pages that follow attempt to explain through example the complex ways that programs are based on human networks, not on theory and scholarship alone. I try to provide a sense of the decisions I made as I determined how best to function within the different institutional settings.

Lipson, Carol. WAC Clearinghouse (2009). Academic>Education>Technical Writing>Business Communication

511.
#30004

Momma, Don't Let Your Babies be Tech Writers

If you have the stomach for it, technical writing can be the path to a full-time writing career. I did it for three years before switching to general business writing, which offers more variety. If you decide to go technical, be sure to keep reading the work of authors you admire so your day job doesn't make you forget everything you ever knew about 'real' writing.

Wormald, Karen. Absolute Write (2001). Careers>TC>Writing>Technical Writing

512.
#32100

monkeyPi's Law

There seems to be a pervasive view that there are two types of writing: 'Noble' (or 'pure') and 'Non-Noble' (or 'technical'). The main problem with that myopic view is that status is immediately connoted. Nobody wants to classify themselves as residing on the non-noble side of the writing world.

monkeyPi (2008). Articles>Writing>Technical Writing

513.
#23445

More on Education for Technical Communicators

For most readers of TC-Forum, technical communication is an activity undertaken by dedicated technical communicators, for whom writing, editing, illustrating, or page-making is their chosen vocation. Yet there is also a much larger community for whom technical communication is only a secondary activity, although it remains an essential part of their work.

Blicq, Ronald S. TC-FORUM (1998). Articles>Education>Writing>Technical Writing

514.
#30338

More than "Correct"

I think it can be dangerous for a technical writer to be a grammar expert.

DeGraw, Yvonne. Boston Broadside (1993). Articles>Writing>Technical Writing>Grammar

515.
#29352

Motivating and Preparing Students to Submit Articles on Technical Writing   (members only)

Technical writing students must learn that technical writing is objective, unemotional, unequivocal, and factual.

Estrin, Herman A. CCC (1974). Articles>Writing>Technical Writing

516.
#34646

Moving into User Research: Establishing Design Guidelines

The best technical writers do user research to understand the audience for their documentation, create user profiles or personas, perform task analyses, and do usability testing to ensure that their documentation meets users’ needs. All of these are activities in which a user researcher engages. Thus, as a technical writer, you can start amassing experience in user research and building a portfolio of user research documentation.

Six, Janet M. UXmatters (2009). Articles>User Experience>Research>Technical Writing

517.
#35849

Moving Technical Authors from Institutional Thinking to Network Thinking

In this video clip, Ecademy’s Thomas Power talks about how business leaders will have to switch between “institutional thinking” (closed, selective and controlling) and ”network thinking” (open, random and supportive). There’s a similar challenge for technical communicators - between traditional “closed” user documents and collaborative, conversational, “open” online user assistance.

Pratt, Ellis. Cherryleaf (2009). Articles>Writing>Technical Writing>Collaboration

518.
#38354

Moving Towards the “Dark Side”: From Technical Writing to Content Marketing

Without a good plan for awareness, many of the other efforts related to technical writing — good user help, a usable interface, accurate requirements, bug-free functionality, and so on, don’t matter a whole lot.

Johnson, Tom H. I'd Rather Be Writing (2011). Careers>Writing>Marketing>Technical Writing

519.
#10681

MS HELP 2.0

MS Help 2.x was announced at WinWriters on March 5, 2001. MS Help 2 is the help system used by Visual Studio .NET help and MSDN Library, and now the Borland .NET IDEs. Getting started with MS Help 2.0? This site is a start.

Helpware.net (2001). Reference>Writing>Help>Technical Writing

520.
#35843

Musings About What’s Really Important

Technical communicators tend to get caught up in tools and techniques and formats. But, as Scott Abel said, It’s not about tech writing. It’s about content.

Nesbitt, Scott. DMN Communications (2009). Articles>TC>Technical Writing>Software

521.
#31109

Musings on User-Generated Documentation

User-generated documentation is a big issue in technical communication circles. If properly done, tapping into the knowledge of users can improve the quality and breadth of your documentation.

DMN Communications (2008). Articles>Documentation>Technical Writing>Wikis

522.
#35277

Must-Follow Trends for Tech Writers

Changes are so massive, so fast, and coming from so many directions that it is impossible to keep up. Still, it’s important to try. For anything that applies to IT applies to tech writing. Writers must be know something about everything and be ready for it. We’re going to have to specialize and collaborate more than ever before.

Norris, Julie. 2moro Docs (2009). Articles>Writing>Technical Writing>Technology

523.
#35127

Must-Follow Twitter Feeds for Tech Writers

The purpose of my blog is to provide tech writers with information about changes and how said changes may impact documentation. That is also the purpose of my Twitter feed. I gather up as much information as I can and pass it on. I've found some excellent feeds to follow related to the various topics of which tech writers need to be aware.

Norris, Julie. 2moro Docs (2009). Articles>Writing>Technical Writing>Social Networking

524.
#35223

My Journey from Technical Writing to Pharma Quality Management

Like most people who entered the technical communication profession in India in the mid to late 1990s, I too became a technical writer more by accident than by design. I enjoyed my technical writing career thoroughly, but slowly moved away, and a decade later, I now find myself heading the Quality Management function at a multi-national clinical research and technology company in India. The career paths of no two individuals are similar. And yet, there are always some common themes in successful transitions from one career path to another.

Narasimha, Kumar. Indus (2009). Careers>Scientific Communication>Technical Writing>Biomedical

525.
#37824

My Long and Winding Road to Technical Writing

I became a technical writer due to necessity, a decision to grow as a person, and sympathy for a dead cat. All right, I suppose I’d better explain that.

Holzworth, Doug. Carolina Communique (2010). Articles>Careers>Technical Writing

 
« PREVIOUS PAGE  |  NEXT PAGE »

 

Follow us on: TwitterFacebookRSSPost about us on: TwitterFacebookDeliciousRSSStumbleUpon