Slashdot Mirror
Do Developers Really Need a Second Monitor?
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?"
Ten points if you read this post on your second monitor like I did!
org.slashdot.post.SignatureNotFoundException: ewg
The second monitor is extremely useful for keeping a browser open for reading Slashdot while I 'work.'
I keep a browser open to slashdot visible all the time. if I didn't have a second monitor, how would I get work done?
You use an LCD Screen! Poofta!
I develop HTML5 based robotic heart surgery machines running on top of jQuery beneath AJAX served by node.js off of an Amazon mounted Rackspace Cloud written in Clojure, and I've had it with LCD Screens, CRTs, and so-called editors.
On even days I punch my code into an ASR-33, and on odd days, I just toggle the code directly into the main memory. And on transcendental days, I use very fine magnets and rearrange the domains on the hard drive.
So don't you get all hoity toity to me about your ability to code with only one screen! You're a bloody wanker is what you are!
In next years Slashdot: Do Stone Tablet Developers Really Need Safety Glasses?