Re: Dual monitors with WDSC

When you can compile a program in less than a second and actually test the
finished product why spend hours doing desk checks? Does the thing work
in our test environment as expected? If Yep then have users test to try
and break it. Then it goes to production. With punch cards and older
tech you had to wait for minutes, or hours for a compile to come back so
you NEEDED to desk check it a lot to make sure you got it.

Dual monitors is not a status symbol, its a productivity gain, and
significant. Of course I would give up my dual 19's or even dual 24's for
1 48 :D


Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777



"Tom Deskevich" <thomas.l.deskevich@xxxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
03/16/2010 09:58 AM
Please respond to
Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries <wdsci-l@xxxxxxxxxxxx>


To
"'Rational Developer for IBM i / Websphere Development Studio Clientfor
System i & iSeries'" <wdsci-l@xxxxxxxxxxxx>
cc

Subject
[WDSCI-L] Dual monitors with WDSC






Don't you know dual monitors is the latest programmer's status symbol?

(I only have one monitor, by the way)

I cannot do the postage stamp size sessions. Even with my bi-focals. :)

I cannot resist, I remember a gentleman telling me he used coding sheets,
and desk checked like crazy, because sometimes the program was not able to
be tested. And went from coding sheets to punch cards to live production.
When I was an operator on an NCR (Not Completely Reliable, Needs Constant
Repair), the programmers had to submit their compiles on punch cards. The
maximum time they had to wait for a compile was 24 hours. Can you imagine
that today???

Today, we have 48" dual monitors and can look at 1000 lines of code at
once.
But the fine art of desk checking and testing seems to have fallen by the
wayside to an extent. We have gotten spoiled. I have a plank in my own eye
as I type this.

Tom Deskevich