Is using a widescreen monitor in portrait orientation more effective for coding?

Tom Kidd picture Tom Kidd · Mar 4, 2009 · Viewed 55.4k times · Source

In the very near future my development setup will be upgraded and part of the deal will be dual monitors (yay!)

At least one of the monitors, possibly both, will be widescreen.

I've heard of developers using a second monitor, especially a widescreen monitor, in portrait mode. It allows for many more lines on the screen (albeit narrower) and runs a bit like having a long page of code.

Does anyone out there use this and think it's more effective?

Answer

Jon Cage picture Jon Cage · Mar 4, 2009

enter image description here

I actually have 3 widescreen monitors in portrait mode and yes, it's a fantastic way to work. There's so much less scrolling around and you can fit all your debug / output / reference windows on screen at once.

The problem with using two monitors is that you'll generally be working on one main one and have output (or whatever on another). If you do have two, set it up so that your primary monitor is directly in front of you and the other (less frequently used) one is off to one side. I find that to be the best way to use a dual-monitor set up as it reduces RSI from being permanently twisted to look at a particular screen.

Additionally, there are some programs available to provide virtual screen splits which I've fund very useful for large/widescreen monitor setups.

[edit] ..and yes, you should write functions short enough to fit on a single page, but being able to see more functions at any one time can often make development easier in my experience :-)

[edit2] Running Visual-Studio-esque IDEs in portrait on a widescreen monitor is fantastic when it comes to debugging compile errors as you have more useable space to see code and errors at the same time. I suppose you could argue that if you compile regularly enough though, you shouldn't see that many errors at one time? ...but who codes like that? ;-)