Re:The problem might not be COBOL
by Spooky23 on Saturday July 11, 2020 @12:06AM
(#23799372)
100% agree. The problems with these systems are usually the crap built around them. The IBM, Univac, Grumman, etc or state people who built this stuff 40 years ago knew their stuff. The operational processes are mature and don’t break.
Usually in a government agency is a layer of VB, J2EE from circa 2003, powerbuilder or some other array of old junk that is responsible for some business processes and is a make work program for hundreds of developers. That is the problem.
Whatever CIO is whining to the governor about COBOL need to be gone, now, and New Jersey needs to find somebody who can get the stuff around the COBOL reengineered and implemented quickly. Then start hacking the COBOL bits apart.
Usually in a government agency is a layer of VB, J2EE from circa 2003, powerbuilder or some other array of old junk that is responsible for some business processes and is a make work program for hundreds of developers. That is the problem.
Whatever CIO is whining to the governor about COBOL need to be gone, now, and New Jersey needs to find somebody who can get the stuff around the COBOL reengineered and implemented quickly. Then start hacking the COBOL bits apart.