"Major Banks and Parts of Federal Gov't Still Rely On Cagey Programmers Who Never Write Decent Comments To Support Programs Instead Of Hiring People To Write Decent Comments."
It's not so much "cagey programmers" as it is over-worked programmers, especially at the State level, where computer illiterate legislators continue to dream up new legislation that puts pressure on coders to modify existing software to meet the legal demands. Except for management, most of whom are computer illiterates as well, State programmers are underpaid and over worked. Many States are having severe financial tax shortfalls, so there won't be new programmers being added to their teams any time soon. I wrote extensive documentation INSIDE my code to explain to any coder who took on my projects after I retired what I did and why I did it that way. Documentation for the users were rarely written because it was the users (clerks) whose functions I was computerizing who dictated what the GUI interface looked like and the underlying software did. If they weren't happy I wasn't happy. So, I didn't need to write documentation for them. They usually trained their replacements and the newbie clerks could ask their fellow clerks if they had questions.
The State Dept of Revenue in the midwest state where I worked have been using a mainframe running COBOL for almost 50 years. About a dozen years ago the suites decided to deploy Oracle as a "replacement". Now they have two database systems and Ellison lies awake nights thinking how to charge more for existing installations. Oracle has ended up costing more in the last decade than the COBOL system has in the last half century. Now they are stuck with Oracle and the taxpayers are stuck with the bill.