Do Developers Really Need a Second Monitor? 1002
jammag writes "It was an agonizing moment: a developer arrived at work to realize his second monitor had been taken (given to the accounting dept., to add insult to injury). Soon, the wailing and the gnashing of teeth began. As this project manager recounts, developers feel strongly — very strongly — about needing a second monitor (maybe a third?) to work effectively. But is this just the posturing of pampered coders, or is this much screen real estate really a requirement for today's developers?"
Second monitors lead to increased productivity (Score:4, Interesting)
So, apparently, says the research to come out of Microsoft's User Interface group. [microsoft.com] Quoting:
They've also found that additional monitors greatly help women in computing. See same article.
My own experience with this is that I perform better when I can get more pixels in my field of view, regardless of screen size, as long as I can read what's going on. An additional monitor improves both constraints. In contrast, when I have to work with a laptop and an 800x600 display, it's like sipping information through a straw. This is regardless of other factors like network bandwidth. Your mileage may vary.
Re:Monitors are cheap, so why not? (Score:4, Interesting)
The cost of buying a second monitor for one developer is immaterial. The cost of buying second monitors for every developer isn't.
Virtual Desktops (Score:5, Interesting)
My money is on the complete lack of virtual desktops on Microsoft's platform.
Yes, there are third party apps that add the capability, but I don't know a single Windows developer who uses them. On the other hand, I don't know a single Linux developer who DOESN'T use them... (now watch Slashdot provide countless counter examples).
Developing on a system without virtual desktops *or* a second (at least) monitor is a huge pain in the ass.
Re:Ten points if reading this on your second monit (Score:3, Interesting)
Re:Well (Score:5, Interesting)