3 ms·

At my current work place (which I'm looking to change, by the way) I work remotely but with a horrible twist. First of all I have to come into the office and s

by Tomis 15y ago

At my current work place (which I'm looking to change, by the way) I work remotely but with a horrible twist. First of all I have to come into the office and stay there for 8 hours a day -which is normal- but then I have to login to another computer via remote desktop and work on that environment, even though I have a perfectly functional computer right in front of me. Things wouldn't be so bad if the remote server wouldn't be a few thousand kilometers away and the lag weren't so noticeable that it induced regular urges to go take a nap and took away most of the desire to write any kind of code. I think most of you agree that anything less than instant response when you type a word or scroll a page is practically torture when done for 8 hours a day. I would have never imagined that it would be possible to have better working conditions at home than at work, but nevertheless here I am, living the horror. One of the things I've learned from this experience is that I still tremendously enjoy programming stuff at home and that when I have a good working environment I can become more productive by orders of magnitude.

arethuza 15y ago
So you go into the office to then work remotely? You have my profound sympathy.
- Tomis 15y ago
  Yeah, that's pretty much it. I've confronted my manager about this and his first answer was an attempt to bullshit me by saying we're working remotely (as opposed to locally) for security reasons; the obvious reply to that monumental pile of crap was to employ my 1337 haX0r skills to copy a whole folder from the remote machine right onto my local desktop (ctrl+C/ctrl+V, actually) - there's your security right there. Working at that place made me a witness to a constant stream of fail.
microarchitect 15y ago
I do this too. I work in the semiconductor industry where I'm told this is the norm. It really sucks.
- nivertech 15y ago
  It's better work remotely even with lagging latency, that dress-up in funny suite and go to the clean room ;)
mgkimsal 15y ago
I've got one project where I need to RDP in to a windows server, then RDP from that one in to another one. The second one is constantly unavailable - 'too many terminal services connections' or something like that. But this is only one client, and it'll be over soon. You have my condolences.
- smiler 15y ago
  Tip: log in to the console. From cmd line : mstsc /v:servername /admin mstsc /v:servername /console admin or console switch depends on version of Windows. One of them will work. Most ppl don't know this. It also has the advantage (in a pinch) that if you need to login to a server, you can log out the current console session and login yourself. Something you can't do with regular terminal sessions (Unless the server is in a domain, and you can connect to terminal services manager remotely and log ppl off)
  - j_s 15y ago
    There are command line tools for logging people off (all of which require the permissions to do so, not so much being on a domain): http://weblogs.asp.net/owscott/archive/2003/12/30/Managing-Terminal-Services-Sessions-Remotely.aspx http://weblogs.asp.net/owscott/archive/2003/12/30/Managing-T... http://www.codinghorror.com/blog/2005/02/remotely-managing-remote-desktop.html http://www.codinghorror.com/blog/2005/02/remotely-managing-r... (be sure to read the comments for additional tips)

by Tomis 15y ago

arethuza 15y ago

So you go into the office to then work remotely? You have my profound sympathy.

Tomis 15y ago
Yeah, that's pretty much it. I've confronted my manager about this and his first answer was an attempt to bullshit me by saying we're working remotely (as opposed to locally) for security reasons; the obvious reply to that monumental pile of crap was to employ my 1337 haX0r skills to copy a whole folder from the remote machine right onto my local desktop (ctrl+C/ctrl+V, actually) - there's your security right there. Working at that place made me a witness to a constant stream of fail.

microarchitect 15y ago

I do this too. I work in the semiconductor industry where I'm told this is the norm. It really sucks.

nivertech 15y ago
It's better work remotely even with lagging latency, that dress-up in funny suite and go to the clean room ;)

mgkimsal 15y ago

I've got one project where I need to RDP in to a windows server, then RDP from that one in to another one. The second one is constantly unavailable - 'too many terminal services connections' or something like that. But this is only one client, and it'll be over soon. You have my condolences.

smiler 15y ago
Tip: log in to the console. From cmd line : mstsc /v:servername /admin mstsc /v:servername /console admin or console switch depends on version of Windows. One of them will work. Most ppl don't know this. It also has the advantage (in a pinch) that if you need to login to a server, you can log out the current console session and login yourself. Something you can't do with regular terminal sessions (Unless the server is in a domain, and you can connect to terminal services manager remotely and log ppl off)
- j_s 15y ago
  There are command line tools for logging people off (all of which require the permissions to do so, not so much being on a domain): http://weblogs.asp.net/owscott/archive/2003/12/30/Managing-Terminal-Services-Sessions-Remotely.aspx http://weblogs.asp.net/owscott/archive/2003/12/30/Managing-T... http://www.codinghorror.com/blog/2005/02/remotely-managing-remote-desktop.html http://www.codinghorror.com/blog/2005/02/remotely-managing-r... (be sure to read the comments for additional tips)