![]() ![]() Whatever you've written has to be tested, and you don't have a trusted source of business logic from which to verify how it ought to work. No one understands how the algorithms work or even how they should work! Forget how challenging it is to work with COBOL, which someone could eventually figure out. That's a huge problem because such an environment very likely does not exist in the world today. Modernization projects require strong leadership and collaboration across many teams. How cooperative do you think these people will be with your efforts? How do you think the managers responsible for this work survive the politics of the project's inevitable failure? Blame rolls downhill. ![]() Imagine working with someone who knows that you are trying to shed light on the technology that they were responsible for, yet do not fully understand. ![]() ![]() Regulatory specifications are ambiguous and disorganized. COBOL systems and the people directly using them are Chernobyl.īoth government regulators and operations personnel have made careers out of trusting black boxes that no one fully understands anymore. It is a career killer with little to no upside. Don't ever work on a COBOL modernization project. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |