[lazylland]

So you're visiting your parents for Thanksgiving, and you get a call "LATCH! there's some issue with the thingamajig that we deployed before you left, urgent fixed required or the universe will ... be okay really; but could you please look into this ? I'll make it worth your while."

The only tool you have at your disposal is your mom's ChromeBox, since you decided to "disconnect" for the holidays.

But no fear ! You log in to a familiar, already configured Orion workspace, debug the shiznit out of the issue, save the day and have well deserved turkey-fueled nap ..

[civild]

Why would you not just remote desktop to your development machine where you have your entire working environment available anyway?

[Flenser]

Because there was a power cut and your development machine isn't online, or the cleaner pulled the plug on it or maybe the sysadmins decided to change the network settings over the holidays.

[Wickk]

The fact that you're making stretches to this situation to stress it's usefulness is not helping anything at all.

[Flenser]

I was replying to the previous comment, trying to say that you can't always guarantee that a remote machine will be available. There are more benefits than just having your development environment always available though, like not needing to install or set up anything when moving between machines, or being able to extend your development environment using the same language that you are developing in.

[lazylland]

Keeping your development machine powered off over the holidays is not really a stretch. Why waste so much power ?

[Wickk]

>or the cleaner pulled the plug on it

[brazzy]

you decided to "disconnect" for the holidays.

But no fear ! You log in to a familiar, already configured Orion workspace

Anyone else see the contradiction?

If you need to disturb people's holidays to have them firefight software problems, the manager manager needs to be fired for allowing such a knowledge bottleneck to form.