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.
>>>-----Original Message-----
>>>From: Andrew Plato [mailto:intrepid_es -at- YAHOO -dot- COM]
>>>
>>>Okay, I am going to say what nobody else will say:
>>>
>>>Telecommuting is great for talented, hard-working people who
>>>are committed to
>>>their work and clients.
>>>
>>>Telecommuting is an abysmal pit of counterproductivity and
>>>waste for everyone
>>>else.
<snip>
Around here, we have quite a few programmers and project managers who
telecommute. At one time or another, these folks were working on-site.
I must say that even with conference calls and net meetings, it is more
difficult to coordinate a meeting if the product coordinator and programmers
are off site, as is the case with my current project. However, these folks
are *always* 15 minutes away by email, or phone if they don't pick up right
away.
BTW, lately, some of these programmers have been broadcasting a *lockdown*
announcement. What I mean is . . . here is an example:
"I apologize for the lack of warning and any inconvenience that may result
from this, but my "door" will be closed and locked for the remainder of
today."
I have seen that kind of announcement several times this week. If they were
in the office and their door were closed, I would knock if I had an urgent
need. Similarly, I will call or email "locked down" programmers if I have an
urgent need.
