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.
> For those that I haven't, including one that they said they were extending
> an offer to me but they just changed their minds, I've often gotten the
> feedback that I "wasn't technical enough".
Certainly there are cases where lots of technical background is helpful if
not outright necessary, but when I've heard a writer described as "not
technical enough" most often it's because engineering was afraid they'd have
to answer a few questions about the software they coded but didn't design or
I once had a tech writing manager tell me she hires only "very senior people
with lots of technical background because sometimes they even have to read
code". In my experience this means:
o the only thing is writing is the code itself
o the manual has to be done next week
o no one will give you the time of day