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'm currently employed as a Tech Writer for an aerospace company with a
software development team of about 15 people. The company has never really
taken a formal approach to documenting their software, but recently hired me
on a contract basis to develop manuals for a number of their applications.
Like a lot of software companies, their primary focus lies with programming,
leaving me much to my one devices when it comes to the documentation
Contract positions with this company have a tendency to become permanent.
However, the majority of these contract-to-permanent transitions have
involved programmers. I'm not sure how they feel about having a tech writer
in-house on a permanent basis.
I know my skills can be put to good use here on a permanent basis, but I
think it might be difficult to convince a company that potentially sees
documentation as a secondary concern to programming.
I'm curious if anyone here has been through a similar situation, and how
they dealt with it. Any suggestions would be greatly appreciated.
IPCC 01, the IEEE International Professional Communication Conference,
October 24-27, 2001 at historic La Fonda in Santa Fe, New Mexico, USA.
CALL FOR PAPERS OPEN UNTIL MARCH 15. http://ieeepcs.org/2001/
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.