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.
Subject:job openings - to list or not to list From:Thom Remington <remingtf -at- ENGG-MAIL -dot- LVS -dot- DUPONT -dot- COM> Date:Fri, 9 Aug 1996 10:06:34 -0400
I agree wholeheartedly that it's appropriate to list job openings. I suggest
the following as guidelines:
o One position per note - or a group of positions, but only if they're
for one employer in one location.
o Location (state) and type of job in subject line. Those not
interested can delete without reading.
o Specific location information in body of note. That is, information
that will tell most folks on the list where the job is. One poster listed
job locations such as "Peninsula" and "E. Bay." OK. Which peninsula, and
which bay? I live on the Delmarva Peninsula, within 60 miles of Delaware
Bay, but I don't think that's where these jobs were.
o Essential information only. Let folks who want more write for more.
o E-mail address - if possible - in the note.
------------------------------------------------------------------------------
Thom Remington remingtf -at- engg -dot- dnet -dot- dupont -dot- com
DuPont External Affairs
Information Design & Development http://www.dupont.com http://www.concentric.net/~remingtf
Speaking for myself, not for DuPont.
TECHWR-L List Information
To send a message about technical communication to 2500+ list readers,
E-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send administrative commands
ALL other questions or problems concerning the list
should go to the listowner, Eric Ray, at ejray -at- ionet -dot- net -dot-
