Skip to main content

Every programmer shall have two monitors - I disagree

While I love the concept of Alex Feldstein: The Programmer's Bill of Rights, I disagree with the first point.

Two monitors? How many USERS/CLIENTS do you know that have two monitors? I deal with a partner who uses two monitors regularly. The result? A bloody pain in the butt every time I try to support them.

I agree - it's cool, it's geeky but it's NOT THE NORMAL ENVIRONMENT THAT USERS SUFFER WITH.

Yes, I said it - SUFFER - users SUFFER with their hardware. Fast - developers need it, comfortable - absolutely - but at least deal with reality.

I remember when Calvin spoke about his notebook in fairly "obvious" terms (not a slight against Calvin, more against the norm) - 4 GB RAM, this was back at the 2002-03 Devcon. Hello? His comment, I remember, ("not that much improved" - or something similar) drew groans from the crowd.

I agree - spoil your developers - but they still need to sit in the world of user reality.

Comments

AlexF said…
Not sure we are talking about the same thing. You taklk about clients. I talk about developers. I do believe that developers (and advanced users if you want to talk about clients), are more productive with two monitors.

The extra real estate is very helpful when you need to have several windows ipopened. I can see code at the same time I have the debugger open while a I'm running a program step-by-step. I can see the code, I can see the output on the program's interface and I can see many windows open in the IDE (properties, variables, whatever).

Works for me in VFP, and in VS2005.
It is also very helpful when I have MS-Outlook open at the same time I'm using a text editor, or -- you get the point.
Andrew MacNeill said…
I realize you were talking about developers - my point is that when developers get two monitors, they have immediately stepped out of the zone of "understanding" what their end users will work with.

I do see the benefit - but I think the danger is where one starts to think everyone has the same thing.

Now then, a larger wide-screen monitor - hmmm...

I'm all about the user experience and I find having too many bells and whistles on my own machines - can then cause possible bad assumptions as to what "regular people" work with.

Of course, I've been proven wrong before...
Anonymous said…
Andrew, I think having a wide screen monitor, as you seem to be lusting after in your comment to Alex, would give you more of a disconnect from the average user than the typical dual monitor setup would. Ahh, "geek lust" - some people would never understand. 8-)

Anyway, the dual monitor setup doesn't "stretch" the screen across the two monitors, it just provides more area to work on. So you still have a representation of what your average user/client is working with - on one of the monitors.

As an analogy, imagine you have the blueprints for your new house laying on your 30" x 60" desk. After you get tired of flipping back and forth between different detail pages, you set a table of the same size next to your desk. Now you can spread out your blueprints and look at them side by side. Having the extra table doesn't stretch the blueprints, it just provides more area to spread out. And you can still understand what your user/client is using to look at his blueprints.

I've been using dual monitor setup for nearly two years. Some of my users also have dual monitors, some don't. And there hasn't been any loss of understanding - just a lot of "monitor envy". 8-)
Andrew MacNeill said…
Boy, it sounds like I'm going to be eating my words and just admit it - I don't have two monitors but I've heard enough about it now to say "hmmm - maybe it's time"

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site: http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older. Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments. But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward. FoxPro VFP

5 Great Reasons to attend Virtual FoxFest

What's coming up? Virtual FoxFest is coming up soon (sessions start October 14th). Like last year, the conference is entirely virtual yet includes great breakdown rooms and sessions to add that nice one-on-one feel that you get in person. It's also staggered so you can choose which days you want to attend - October 14th, 20th and 26th. This is great if you can't break away for a consecutive three days. But really, I've gone through the sessions and I see five great sessions that I'm eager to check out. 1. A Decade of Thor (Rick Schummer) Thor has been an extension for Visual FoxPro that many developers swear by, yet many don't know even exists. Visual FoxPro's built-in extensions are great but Jim Nelson's Thor supercharges your IDE. I can't believe it's been ten years - so Rick's session should be able to not just whet your appetite but give you all the reasons you should be using it. 2. VFP C++ compiler.  Last year, we saw DotNetX as well