College class project COBOL was NOTHING like working on years old ( or
decades old O_o ) production COBOL. It usually entailed going on an
archeological dig through source, trying to discover business rules that
nobody left on the devl team could remember.
Also re-discovering why some pieces were "architected" the way they were.
Those brave kids will earn any high $$$$ with blood, sweat, and many many
tears.
TKilling
On Tue, Feb 17, 2015 at 2:27 PM, Mike Stein <mhs.stein at gmail.com> wrote:
----- Original Message ----- From: "Roe
Peterson" <roeapeterson at gmail.com>
To: "General Discussion: On-Topic and Off-Topic Posts" <
cctalk at classiccmp.org>
Sent: Tuesday, February 17, 2015 1:54 PM
Subject: Re: Rich kids are into COBOL
I wouldn't wish a COBOL career on my worst enemy. What a god-awful mess.
And yes, I know how and why it came to be. And all about legacy code
bases and the high cost of migration. I was forced to take cobol back in
1978, never attended a lecture, handed in all the assignments, wrote the
final, passed the course, and promptly forgot the whole thing.
Still, what a god-awful mess :-)
----- Reply -----
Good thing Grace Hopper isn't around to read that...
I actually kinda liked COBOL; a lot of it was just boilerplate after all...
m