<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Hewitt, John</title>	<link>http://tc.eserver.org/authors/Hewitt,_John</link>
	<description>A bibliography of works by Hewitt, John in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Hewitt, John</title>
		<link>http://tc.eserver.org/dir/Hewitt,_John</link>
	</image>
	<item>
		<title>A Career in Technical Writing: Beach Time</title>
		<link>http://tc.eserver.org/31901.html</link>
		<guid>http://tc.eserver.org/31901.html</guid>
		<description>Beach time and bench time refer to paid or unpaid time off between consulting contracts. When you are a contractor, it is best to take initiative and find other options no matter how much you trust your recruiter. Never trust a company to have your best interests in mind.</description>
	</item>
	<item>
		<title>A Career in Technical Writing: Life as a Wannabee</title>
		<link>http://tc.eserver.org/31898.html</link>
		<guid>http://tc.eserver.org/31898.html</guid>
		<description>I couldn’t picture myself as a big time advertising writer, but technical writer was something that I figured I could do. I had plenty of computer experience. Half of my personal debt was related to computer equipment. I had been on the Internet since before there was a World Wide Web. I had a degree in creative writing and I had been an editor and writer for a few minor publications. Technical writer seemed obtainable.</description>
	</item>
	<item>
		<title>A Career in Technical Writing: Two Dates to the Prom</title>
		<link>http://tc.eserver.org/31899.html</link>
		<guid>http://tc.eserver.org/31899.html</guid>
		<description>In the world of contracting, the entire hiring process can take place over the phone. Knowing the right tool (even a little) can get you the job.</description>
	</item>
	<item>
		<title>Why Writing Deadlines May Be (Almost) As Good As Money</title>
		<link>http://tc.eserver.org/31902.html</link>
		<guid>http://tc.eserver.org/31902.html</guid>
		<description>As much as we all like and/or need money, getting paid may not be enough to keep a writer motivated. Deadlines often are just as important. Although some of us fear — or even hate — them, the truth is that without them many of us simply wouldn’t write anything. And you can count me among those many.</description>
	</item>
	<item>
		<title>How to Find Technical Writing Jobs</title>
		<link>http://tc.eserver.org/30643.html</link>
		<guid>http://tc.eserver.org/30643.html</guid>
		<description>There are some key differences between looking for publishing jobs and looking for technical writing jobs.</description>
	</item>
	<item>
		<title>Technical Writing Part Five: Education</title>
		<link>http://tc.eserver.org/25598.html</link>
		<guid>http://tc.eserver.org/25598.html</guid>
		<description>Education and skills development are vital to a technical writing career. While there are no set-in-stone educational requirements for a technical writer, there are very few writers in the field who do not have a college degree.</description>
	</item>
	<item>
		<title>Boilerplate</title>
		<link>http://tc.eserver.org/25015.html</link>
		<guid>http://tc.eserver.org/25015.html</guid>
		<description>The SMEs had a choice between two sets of tables they could use to input key product data. If their part of the project used items from the A list, they were supposed to use table A. If their part of the product used items from the B list, they were supposed to use table B. In almost every case, the SMEs used the wrong table, leaving gaps where their information did not conform to the columns of the tables. </description>
	</item>
	<item>
		<title>The Basics of Book Profits</title>
		<link>http://tc.eserver.org/25008.html</link>
		<guid>http://tc.eserver.org/25008.html</guid>
		<description>Most writers have no idea how much money they can expect when their book is published. The formular, however, is fairly straightforward. To begin with, a writer generally receives an advance. An advance is payment, in advance, based on the expected initial earnings of the book.&#xD;&#xD;Royalties (ranging from 4% to 8% in most cases) are generally based on the cover price of the book, but that does not include books that are discounted or remaindered. So, for the sake of argument, say you sold 20,000 full-price copies of a paperback priced at $7 (I know it would more likely be $6.95 but I am going to use round numbers.) If your royalty percentage were a generous 8% you would make a total of $11,200.</description>
	</item>
	<item>
		<title>Technical Writing FAQ</title>
		<link>http://tc.eserver.org/25007.html</link>
		<guid>http://tc.eserver.org/25007.html</guid>
		<description>What are the primary skills of a technical writer?&#xD;How do I become a technical writer? &#xD;</description>
	</item>
	<item>
		<title>Twelve Exercises for Improving Dialogue</title>
		<link>http://tc.eserver.org/25010.html</link>
		<guid>http://tc.eserver.org/25010.html</guid>
		<description>Dialogue is one of the most difficult aspects of writing to master. There are many pitfalls you must try to avoid, such as:&#xD;&#xD;Stilted language&#xD;    Dialogue that does not sound like natural speech.&#xD;Filler&#xD;    Dialogue that does not further the scene and does not deepen your&#xD;    understanding of the characters.&#xD;Exposition&#xD;    Dialogue that has the character explain the plot or repeat information&#xD;    for the benefit of the audience.&#xD;Naming&#xD;    Having one character use another character’s name to establish identity.&#xD;    People almost never say other people’s names back to them, and if they do it&#xD;    is a character trait typical of a used car salesman.&#xD;Overuse of Modifiers&#xD;    Too many dialogue modifiers such as shouted, exclaimed,&#xD;    cried, whispered, stammered, opined, insinuated,&#xD;    hedged and a million others. Modifiers such as this can sometimes be&#xD;    useful, but are often annoying and used as a crutch for poorly designed&#xD;    dialogue. </description>
	</item>
	<item>
		<title>Document Hack (A Technical Writer&apos;s Journal): Changing Bosses</title>
		<link>http://tc.eserver.org/24991.html</link>
		<guid>http://tc.eserver.org/24991.html</guid>
		<description>Switching bosses within the same company is not an entirely smooth process. On the day of the crossover, I showed up to work and discovered my badge and my email deactivated. It took most of the day to get security to reactivate my accounts.</description>
	</item>
	<item>
		<title>Contracting for Fun and Profit</title>
		<link>http://tc.eserver.org/24989.html</link>
		<guid>http://tc.eserver.org/24989.html</guid>
		<description>Because I am working at this job through a contract, rather than as a regular employee, there are some situations unique to my position. In the technical writing industry, many writers work on a contract basis through an agency. This type of employment is called contracting, although you may also hear it called consulting. I prefer the term contracting because I associate consultants with people whose job is to advise a company on one issue or another. That may or may not describe a particular technical writing assignment.</description>
	</item>
	<item>
		<title>Document Hack (A Technical Writer&apos;s Journal): First Day</title>
		<link>http://tc.eserver.org/24987.html</link>
		<guid>http://tc.eserver.org/24987.html</guid>
		<description>Rule number one for a contractor is to never panic about what happens your first day. First days are naturally chaotic, and often companies are not fully prepared for you. Because contractors are usually brought in to solve a particular problem, the people are anxious to get you started, but companies, especially large ones, are not geared for quick action.</description>
	</item>
	<item>
		<title>From Acrobat to FrameMaker</title>
		<link>http://tc.eserver.org/24990.html</link>
		<guid>http://tc.eserver.org/24990.html</guid>
		<description>FrameMaker is the industry standard for writing book-length documents. It is a powerful program capable of creating books of well over a thousand pages. The learning curve for the program is significant. FrameMaker is a much different animal than Microsoft Word and other word processors.</description>
	</item>
	<item>
		<title>Document Hack (A Technical Writer&apos;s Journal): Interview and Negotiation</title>
		<link>http://tc.eserver.org/24986.html</link>
		<guid>http://tc.eserver.org/24986.html</guid>
		<description>My face-to-face interview with the company was similar to my phone interview. So similar, in fact that more than once I found myself answering the same questions I had answered over the phone. They did throw a couple curve balls at me, however. The strangest question I was asked was, &apos;If we called your references, what would they say about you?&apos; I was unprepared for this one, and I ended up talking more about my references than about what they would say about me.</description>
	</item>
	<item>
		<title>Document Hack (A Technical Writer&apos;s Journal): Phone Interview</title>
		<link>http://tc.eserver.org/24985.html</link>
		<guid>http://tc.eserver.org/24985.html</guid>
		<description>When I originally spoke to the recruiter on the phone, she gave me a brief description of the job and asked for my rate. We negotiated the rate for a few minutes and came up with an acceptable number ($25 an hour) and she sent me an e-mail with the full job description and a short agreement asking me to confirm her representation and my rate. I sent back my confirmation and that was it for a while.</description>
	</item>
	<item>
		<title>Document Hack (A Technical Writer&apos;s Journal): The Acrobat and the Illustrator</title>
		<link>http://tc.eserver.org/24988.html</link>
		<guid>http://tc.eserver.org/24988.html</guid>
		<description>Using Acrobat, you can make minor edits to a PDF file, but Acrobat documents are very sensitive. Typing a single character can throw several lines off, destroy tables and cause all sort of other troubles. Alternately, it can be relatively uneventful and painless. You will not know until you type in that character.</description>
	</item>
	<item>
		<title>Technical Writing: A Technical Writer&apos;s Skill Set</title>
		<link>http://tc.eserver.org/24981.html</link>
		<guid>http://tc.eserver.org/24981.html</guid>
		<description>Discusses writing skills, technical skills, tools skills and other skills.</description>
	</item>
	<item>
		<title>Technical Writing: Desktop Publishing Tools</title>
		<link>http://tc.eserver.org/24982.html</link>
		<guid>http://tc.eserver.org/24982.html</guid>
		<description>The production of printed documents using a computer is called desktop publishing. At its most basic, desktop publishing requires a computer, a printer, and some sort of text or graphics program. While you can achieve desktop publishing using something as simple as a word processor, the applications used by technical writers are often more sophisticated and expensive than those used for common office applications. Because technical documents are often longer and more graphically complex than general business or personal documents, they require programs that are designed to handle these tasks. When technical writers do use common office applications, they are frequently required to use features that most users never need. For example, Microsoft Word has index and table of contents tools. Those tools aren’t very flexible and can be difficult to use, but if Microsoft Word is the only desktop publishing application at your disposal you may find yourself putting those tools to use.</description>
	</item>
	<item>
		<title>Technical Writing: Education</title>
		<link>http://tc.eserver.org/24983.html</link>
		<guid>http://tc.eserver.org/24983.html</guid>
		<description>Education and skills development are vital to a technical writing career. While there are no set-in-stone educational requirements for a technical writer, there are very few writers in the field who do not have a college degree. There are occasional exceptions to this rule (Some companies provide in-house training, generally to employees who have lost their current position due to a restructuring such as the closing of a manufacturing plant), but for those wishing to enter the field, an academic education is essential.</description>
	</item>
	<item>
		<title>Technical Writing: How to Find Technical Writing Jobs</title>
		<link>http://tc.eserver.org/24984.html</link>
		<guid>http://tc.eserver.org/24984.html</guid>
		<description>Step One: Be Qualified&#xD;Step Two: Demonstrate Your Qualifications&#xD;Step Three: Make a Contact List&#xD;Step Four: Call the Employers&#xD;Step Five: Master the Interview&#xD;Step Six: Follow Up&#xD;Step Seven: Go Back to the Beginning</description>
	</item>
	<item>
		<title>What a Technical Writer Writes</title>
		<link>http://tc.eserver.org/24979.html</link>
		<guid>http://tc.eserver.org/24979.html</guid>
		<description>he range of writing a technical writer performs varies widely. Much is dependent on the technical specialty of the writer and of the needs of the company. You may find yourself a part of one large project, or overseeing dozens of smaller projects. You might write manuals, articles, proposals, white papers, product descriptions or any of a hundred other types of documents.</description>
	</item>
	<item>
		<title>Freelance Jobs</title>
		<link>http://tc.eserver.org/24992.html</link>
		<guid>http://tc.eserver.org/24992.html</guid>
		<description>A weblog of writing and editing jobs.</description>
	</item>
	<item>
		<title>Living Documentation: The Future of Technical Writing</title>
		<link>http://tc.eserver.org/10825.html</link>
		<guid>http://tc.eserver.org/10825.html</guid>
		<description>Living documentation is documentation that does not cease to be developed until the product ceases to develop. Living documentation can be produced at any time in multiple formats. The book, web pages and online help would continue to be developed as long as that development either solves inaccuracy or increases product usability and customer satisfaction.</description>
	</item>
	<item>
		<title>Technical Writing: Overview</title>
		<link>http://tc.eserver.org/10001.html</link>
		<guid>http://tc.eserver.org/10001.html</guid>
		<description>Technical writing as a field covers many different areas. Many people, when they think of technical writers, think of user manuals for their favorite (or least favorite) software application. That is certainly one job a technical writer might have, but it is far from the only job. Some technical writers spend much more time working of reference materials, which can take the form of long books filled with technical information but very little in the way of instructions. Some technical writers spend their time creating online help files for people with specific problems that occur within an application. Other technical writers rarely work on new information at all; they spend their time updating old manuals or datasheets. Many technical writers work on a large team focused on creating a single document or set of documents. Other technical writers find themselves in charge of every single technical document an organization produces. A technical writer may create a single sheet of information or a thousand page book. The occupation is very diverse.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Hewitt,_John.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>