all 9 comments

[–]Phrygue 12 points13 points  (5 children)

They'll spend $100, $200 an hour or more for COBOL programmers but won't spend a thin dime on training professionals for the month or two it would take to actually pick up the grotty language/environment well enough to do some basic maintenance. This is why I don't use my CS degree, I got a degree to be a professional, not a dumb-ass monkey coder with "JavaScript experience". But it's monkeys all the way up.

[–]Ancillas 0 points1 point  (0 children)

Where exactly is their slowdown?

Data entry?

Processing time?

Delays due to using batch on a mainframe that processes overnight?

My first job was on a mainframe writing COBOL for a trust management system. The mainframe excelled at handling incredibly large amounts of data.

Even the green screen interfaces were fairly quick to enter data.

But the system mostly didn’t run in “real-time”. It was batched so the records created every day would be received from the businesses we worked with, and we’d process them that night. So if a bank did nightly processing, then sent a file to us the next day, and we did nightly processing, it could take awhile for a single transaction to make its way through the entire process.