development environment - Developing via Remote Desktop -

Is there any successful comment about the team working through a remote desktop?

In many workplaces, we put end users through Citrix and the applications on a central, powerful server are sometimes the same as the server in the same building, but often they are remotely Are there.

My developers can get some big advantage for Windows XP or Vista installers to run on two servers, Hyper-V

I am concerned that through the Internet, the RDP / RDC will be able to develop someone very efficiently.

I'm sure I can hear a lot of bad things about it ... are there any people who have success?

I have a situation where efforts were made to do this with the satellite office. This was done for the Java development team using various Java IDE tools. The result was not considered as a success, and the company brought the team to the central London office for a long time.

To do this on a day-by-day basis on interactive software, the result is not really very enjoyable, for some things that the text-based tools such as the main of the vim and unix command line tools Uses it, it works better to some extent. At one point, I was passing through XVNC one 128 kbt DSL link (one type which was then prevalent in New Zealand) and could work on an oracle-based data warehouse at a remote location. The level of interactivity required for tooling makes them very sensitive to slower links compared to Windows-based IDEs.

Therefore, I will add the argument 'It depends' with some merit:

• I will not recommend it for a modern IDE, and of course Not for heavy graphical things like Dreamweaver, BI development studio or informatica.

• Perhaps for a text environment such as traditional Unix development tools it can be done to work quite well. These user interfaces are less sensitive to delays than direct-manipulation user interfaces.

I am a believer in 'best tool' theory To give a second-level user interface to any development team, will go out of their way and give a negative signal. Doing this is likely to reduce cost savings and it will be upset by some members of your team even if it works well enough If you can make it, you are still making a price statement by doing so.

The weight of cost savings against the cost of changing one or more key development staff.