Re: Work remote

I suspect it is more than just a control issue though.  For many projects it is 
essential for the programmer to be there, on site, to stay on track and to 
reflect the nature and culture of the establishment.  Even the grunt work of 
Y2K conversions needs a certain amount of it.  The other problem I've noticed 
is that management has a helter-skelter schedule and it may be impossible for 
them to meet and review work and projects on a timely basis.  Therefore it is 
in their interest to have the programmers at a desk they can find when their 
schedule allows.

What does astound me though is the willingness of these companies to pay 
obscene amounts for a contractor's services and then put the contractor on an 
upended soda case and an old 14" 3196 terminal hauled out of dead storage while 
regular staff is using new Pentium 233s with 17" monitors.  Its their money so 
I guess it is their rules, but still...



In <4db47add.364f0504@aol.com>, on 11/15/98 
   at 11:44 AM, HankHeath@aol.com said:


>My response was that I would be happy to work remotely. However, the
>company management nixed that due to control issues, which I cannot
>entirely disagree with.

>So, a follow up question: are many of you getting opportunities to work
>on AS/400's remotely? I know the technology is there. Just a matter of
>management being flexible enough to work with you, in my humble opinion.

-- 
-----------------------------------------------------------
boothm@ibm.net
Booth Martin
-----------------------------------------------------------

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---