At the time, he was making $100,000+ and taking time off whenever he wanted. I think he made a lot more during the fixes that prevented #Y2K from becoming the expected meltdown, but he then ran into headwinds because foreign programmers were being imported to do the work for a lot less than what he was accustomed to earning, so he retired.
I thought about this back when the lockdowns geared up and state governors were crying about lacking the COBOL programmers to fix their unemployment insurance systems.
Assuming the demand for COBOL programmers still exists and is expected to continue for several years, there is one more big step that is needed. The companies that have these openings need to widely publicize their openings, so that recruiters and potential COBOL programmers will see the demand in their job searches. Visit college campuses on career day and tell students "we don't have openings for X programming language, but if you have skills in X, we will hire you and train you to program in COBOL". Tell the campuses that $COMPANY doesn't need more cloud engineers (or whatever chools are advertising now), but that the company could definitely use more COBOL programmers.
If they do this enough, colleges / universities, and boot camps will start training people for the high paying jobs that the industry is offering.
after a nuclear war, the remaining people will probably not be able to spin up a modern operating system on their improvised chips. How do you build a simple, reliable, legacy-free OS from scratch? What ideas 💡 and techniques should be passed down to those people?
If we think hard enough about this, I think we’ll agree that closed-source systems are basically designed to be almost impossible for people outside the sponsoring organization to reproduce (for an example, consider [ReactOS](https://reactos.org/), which launched as [a project to produce a system compatible with Windows 95](https://reactos.org/wiki/FreeWin95) and [then changed to focus on Windows NT](https://reactos.org/wiki/ReactOS/History), and after more than 25 years, is still not capable of being a daily use system.
But we may also determine that most open-source systems are likewise not designed in such a way that reconstruction is viable. The Linux kernel is *huge* these days.
Additionally, in my opinion, they’d probably want to use programming languages designed for readability, ease of learning, and error-reduction first (that is, more like #COBOL than #C, more like #Java than #CPlusPlus, more like !Smalltalk and #Lisp / #Scheme than #Perl / #Raku and #JavaScript) and then performance and low-level access.
I think it is a mistake to assume that one could start with a modern version of #gcc or #llvm or #msvc … because it is not a given that the software itself and someone who knew how to use it (and update, modify, and adapt it) would still exist.
I’d type in my program and get fifty or seventy five errors. It would turn out that most of those errors were really cascading from me putting the sections in the wrong order or starting a line in the wrong column.
I did not get a good grade in that course. I’ve always wanted to try COBOL again, just to see whether it was just the fact that I was too broke to buy a computer and compiler.
I went back to my business courses and eventually earned a degree.
I’m thinking about all the different programming and scripting languages I studied years ago. Years later, I can’t even tell you how to put the sections of a #COBOL program in the right order or how to tell what you were trying to do in a #Perl script or what to change in this decaying pile of #PHP in order to retrieve all posts in each conversation.