COBOL predates Agile by 42 years. Why does Fiserv insist on forcing COBOL devs to drink the Agile koolaid?
11 replies (most recent on top)
No one heard of Guy hiring his buddy gerry Demarco to clean up mainframe security and awarding gerry's consulting company a multi million dollar contract to do the work? Not sure how that's not a conflict of interest. But I guess if you're friends with Guy....
Also about DevSecOps. Sure it’s better together. But Agile can still be beneficial in cases where DevSecOps isn’t used or used yet, and even outside of IT.
Couple things…
Agile ideas and methods started to emerge way before the Manifesto for Agile Software Development, some emerged with the development of mainframe computing.
You can absolutely use Agiile approaches in COBOL development.
Fiserv probably needs a new stack in some areas but some of the old COBOL might not be bad to keep.
Doing Agile is not just software but like someone else wrote included new ways of managing too.
Just don’t blame COBOL is what I mean
People forget Agile is nothing without DevSecOps. Both have to be combined to reap benefits.
Agile is not just about software.
Frank and Guy love wasting big bucks on agile as a way of accelerating the rate of attrition.
The mainframe has had containerization for 30 years. But it’s a big deal for the .net crowd, I’m told they’ll be there in 5 years :-)
COBOL rules. All the backend code you have stored as objects in your Oracle DB.
Agile is as agile does.
They want to get rid of all the support positions around the developer. Then the developer will do all the research, make all the decisions, and do all the testing. What could possibly go wrong?
So that you can finally speed up from the snails pace
Maybe to start building a new technology stack?