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:Re: Learning C code as a technical writer From:Win Day <winday -at- IDIRECT -dot- COM> Date:Mon, 13 Nov 1995 15:42:38 -0500
>Second, where I work, engineers are treated like gods. We are a hardware
>driven company, whatever that means, but software engineers, especially to
>produce the BIOS that wakes up all the chips, are in great demand. We can't
>hire enough good engineers, hardware or software. When we do, we steal them
>from somebody else. Writers, are, well, easier to find. What my boss thought
>we really want are writers that also have a bachelor's degree in electrical
>engineering, but I had to point out that if they had an engineering degree,
>they'd be better off getting paid to engineer, not to write. The delta has
>to be $25,000 per year more for engineers than tech writers. So, we've
>decided that the next writer should at least have an Associate's degree in
>electrical engineering. Which means *I* couldn't even get hired.
Either your engineers are WAY overpaid, or you as a technical writer are WAY
I'm a chemical engineer; I had 8 years of engineering experience before I
switched to technical writing 3 years ago. I earn more per hour as a
technical writer than I ever did as an engineer.
Just my $0.03 CDN (about $0.02 US).
Email: winday -at- idirect -dot- com