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 have an interview next Wednesday, but I think that they're calling this
position a Systems Analyst and it is scheduled to start September 3. My
currently approved, but in a holding pattern contract, is also supposed to
start September 3 and that one is a Business Analyst. Both are with the
State. If I get the Systems Analyst position, then I may need to work
nearly 80 hours a week for a bit because of the delays in the State budget.
Oh well.
I can see that respect for Technical Writers is really starting to fade, but
respect for people that think before they document, like Analysts, is
starting to well. (Maybe, one day, there will be a position called,
"Analysis Writer" or "Analytical Technical Writer.") So maybe the State has
been burned by hacks because it now requires detailed written and oral
descriptions of past positions as they apply to the work order. I have to
jump through hoops because of hacks that have gone before me.
Is this what you are asking me to imagine?
Lauren
> -----Original Message-----
> From: John Posada [mailto:jposada01 -at- yahoo -dot- com]
> Sent: Sunday, August 12, 2007 9:45 AM
> To: Lauren; Richard Lewis; Gene Kim-Eng; techwr-l -at- lists -dot- techwr-l -dot- com
> Subject: Re: Monkey Business
>
> ...and after having the customer exposed to one, why we have
> such a hard time fighting for respect. Imagine walking into a
> gig right afterwards?
>
> Again, this is only based on what we've been exposed to on this list.
>
> John Posada
> Senior Technical Writer
>
> "They say everyone needs goals. Mine is to live forever.
> So far, so good."
>
>
> ----- Original Message ----
> From: Lauren <lt34 -at- csus -dot- edu>
> To: John Posada <jposada01 -at- yahoo -dot- com>; Richard Lewis
> <tech44writer -at- yahoo -dot- com>; Gene Kim-Eng <techwr -at- genek -dot- com>;
> techwr-l -at- lists -dot- techwr-l -dot- com
> Sent: Sunday, August 12, 2007 12:34:39 PM
> Subject: RE: Monkey Business
>
>
> Well, now I know what a technical writing hack looks like, or
> at least I've
> seen the posts of one.
>
> Lauren
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-