Telecommuters and Downtime?

clearcache asks: "I'm a new telecommuter. My wife and I, former New Jersey residents, moved to a Midwestern city in January. I remain employed with the same NYC company that I worked for when we lived in Jersey. Aside from the normal moving hassles, I experienced some connectivity issues due to the complete incompetence of my telephone company. These issues repeated themselves, and, due to the lack of a good problem escalation policy on their end, it took quite some time to get them resolved (some are not yet resolved!). These problems resulted in a serious loss of time on the job. When I approached the phone company to discuss compensation for downtime, they responded that, since it is a residential line, they do not compensate for downtime. With more and more people telecommuting, it's only a matter of time before the blurred distinction between 'residential' and 'business' telephone lines becomes an issue. Has anyone had experiences like this? If so, what did you do? Does anyone have any general advice about telecommuting and pitfalls that I should avoid in the future? How do the companies that you work for deal with your downtime?" When my connections to the 'net fail and I can't find someplace in the area where I can leech some bandwidth, I am forced into taking the day off. Fortunately for me, Blacksburg, VA is extremely well connected for its size and such occurances have remained rare. How do you telecommuters out there deal with those Bad Computing Days, where for one reason or another, things just refuse to work?

Comments

I don't really see the big problem.

[JanneM]

It depends on what your work is, of course, but I would simply make sure that I can get work done even with a net outage. Mirror essential documents or code pieces locally, and you can get something done anyway. There is always documentation to write, proposals to tinker with or reading to catch up on. And if you need to talk to a colleague, there's always still the telephone...

/Janne