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.
Assuming that you already have a general grounding in computer
technology (if not, get that first)...learn the programming language(s)
that is/are used by the developers in your company.
If your company's products are software tools for customers who then use
them to write their own software, then learn LOTS about the language.
If the products are intended for end-users only, then an intro-level
course in the language will be useful. You don't have to become a
full-fledged codehacker... but knowing something about the language &
tools your software developers use will give you insights into how your
product works, and why it works the way it does.
If the language is object-oriented (Java, C++, . . .) then add a course
or two about object-oriented analysis & design, if such a course is
available.
--------
Ernie Tamminga
Director, InfoEngineering
Digital Sound Corporation
-----------------------------------------------
Opinions expressed are my own, and not necessarily those of Digital
Sound Corporation
>-----Original Message-----
>From: Tracy Jones [SMTP:jonest -at- IPIX -dot- COM]
>Sent: Thursday, June 12, 1997 7:58 AM
>To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
>Subject: Course wish list?
>
>I have a degree in English with a concentration in writing. As far as my
>school (U. of TN at Knosville-- Hi Pat) was concerned, there is no
>difference between what I learned and what a budding tech writer there would
>learn. I, however, took many hours of poetry and fiction writing and exactly
>three in nonfiction, none of them technical. I've freelanced feature stories
>for about five years (and still write fiction, something that amuses the
>engineers), but except for a bit of dabbling in business writing, this job
>is my first experience in technical communications.
>
>My question: one of my benefits here is that the company will pay for
>continuing education, whether that's just a few computer science courses,
>or, conceivably, a graduate degree. I'm eager to start taking classes, and
>I'm kicking myself that I avoided all technical subjects like the plague.
>What kinds of classes would you take? I work for a software company but
>would also like to learn skills that could be applied to other types of
>technical writing environments.
>
>Thanks in advance,
>
>Tracy
>
> TECHWR-L (Technical Communication) List Information: To send a message
>to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
> to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
> Search the archives at http://www.documentation.com/ or search and
>browse the archives at http://listserv.okstate.edu/archives/techwr-l.html
TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html
