@estherschindler Yes, don't forget that old saying: Cobol corrupts the brain.
@gecole
I think with adequate planning and employment of people who are close to retirement and have a proven resistance against Cobol brain damage, it should be possible to set up a responsible and serious migration to protect future generations of programmers.
It's true for anyone code.
Screw the whole idea of move fast and break things!
It's not even correct in technology.
Test. Test. Test. AND NEVER WITH PRODUCTION DATA.
@JohnJBurnsIII @estherschindler give me a P-O-C, a fully signed solution design, statement of works & rollback strategy with a full support document set & training guides, or give me death...
@estherschindler Working code doesn't get weaker - if it ain't broke, don't break it.
I can't tell you how often I have to fix mysterious bugs in code as it is ported from one architecture to another - never mind a rewrite in a different language.
Hubris or stupidity - we will never know.
@estherschindler ding ding ding ding. We have a winner
@estherschindler my wife did too and she's an artist. But she's loved an IT nerd for over thirty years.
Don’t forget the JCL!
@estherschindler funny story, SSA.gov was down from March 31st until today. Let working cobol work
@writermissyo Really? Can you cite a source?
@estherschindler I went to log in every day to my SSA account (I receive social security disability payments) and there was an error every time you went to log in. And the system auto logs you off after like an hour.
Checks and balances AND CODE
@estherschindler I mean, it would align with my financial interests, but that's not really a good reason for that.
@estherschindler oh my... Sooo true...
@estherschindler
I use many RiiR (Rewrite it in Rust) tools, but I can't say he's wrong.
Missing period.
@jchaven Now THAT is a great COBOL comeback!
@estherschindler You laughed, I got shivers down my spine and my hair stood on end.