TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
I totally agree with David. This is what I was going to suggest. Don't worry
about not having portfolio pieces that you wrote for pay. Find something to
document, and write about it. People need to see that you really can do a
good job of tech writing.
They'll also probably be impressed that you had the motivation to do this on
your own. It shows how much you want the job, and how interested you are in
tech writing, which definitely counts.
I can think of a few applications that have no printed user manuals. One is
Hypersnap, the $20 screen capture program I use. It has a help system of
sorts, but it ain't the greatest. Try writing a manual that would explain
how to use the program to a complete beginner, someone who's never made
screen captures. Also make sure you provide navigation elements that allow
experienced users to skip over the beginner stuff and get straight to the
how-tos, so they can be using the app in five minutes (with Hypersnap, that
is possible). Then all types of users should be happy.
Don't be verbose, get to the point, and sound friendly, because people using
a strange new app need encouragement.
When writing new docs, try not to rely on the existing help system. Instead,
USE the app and see how YOU think it should be explained. Get a fresh point
of view. That's the same thing you'll be doing on the job as a tech writer
(at least in the best computer tech writing jobs, IMO). Then you can use the
existing help system to find more subtle things about the system that you
may not have noticed.
Beth Kane
Senior Communications Specialist
bethk -at- personalgenie -dot- com
www.personalgenie.com
Tucson
----- Original Message -----
> I recommend writing up some procedures in Word or FrameMaker about
software
> or hardware with which you are familiar. Do about five to ten pages. This
> number will give you a chance to show off both your procedure-writing and
> organizational skills. Be sure to include illustrations (screen grabs or
> line art) and format the document as if it were a finished product.
> You can then say, "See, I can do it!"
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Develop HTML-based Help with Macromedia Dreamweaver! (STC Discount.)
**NEW DATE/LOCATION!** January 16-17, 2001, New York, NY. http://www.weisner.com/training/dreamweaver_help.htm or 800-646-9989.
Sponsored by SOLUTIONS, Conferences and Seminars for Communicators
Publications Management Clinic, TECH*COMM 2001 Conference, and more http://www.SolutionsEvents.com or 800-448-4230
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
