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.
Now here's the story. My company has been bought out recently, and pretty
much everyone except Development moved down to San Diego to snuggle up with
the parent company. The rest of us stayed up here in L.A., land of our
birth. Well now, TPTB have finally decided it would just make more sense to
have everyone all in one place, which is probably true, although it is going
to mean a terrific turnover in programmers and analysts and--yes--this one
lone writer.
Now the good thing is they love me here, and have offered me an
extraordinary opportunity. I'm going to be telecommuting, which I love (I
may never have to put on shoes again) but I'll be physically very distant
from the daily hubbub of the designers etc., 150 miles away, which is making
me slightly uncomfortable. Oh, I'll be heading down the coast for meetings
a couple of times a month, they say. That's good. It's a nice drive. But
it's not the kind of thing where you can just drop in for a walkthrough.
So my question is this. I'm a little uncertain about how well this is going
to work, being so far out of physical contact for fairly long periods. Do
any of you long-distance telecommuters have any sage advice on how to make
this work?
Cheers!
Maggie Secara
msecara -at- cayenta -dot- com
"All the world's a stage, Mick, but some of us are dreadfully
under-rehearsed."
