Looks as if just about everybody on LuLa was a programmer.
That link is a hoot, Jeremy. Actually, there's some truth to that farce. If you swallow the whole C++ enchilada you can cause yourself some problems, but in general it's a step in the right direction. C# is even better because it's designed to keep you from making some of the mistakes you're almost bound to make in C++. My grandson tells me there are later iterations that are even more foolproof (though you gotta remember there are a lot of fools out there).
And Eric, years ago I knew an older guy who was making a bundle maintaining Cobol stuff for banks. Younger folks simply didn't know Cobol, and the banks had sunk fortunes into their creaky Cobol systems and weren't about to dump them, so the guy had a huge market and not a lot of competition. He was laughing all the way to the bank. I thought about trying it, but I really disliked Cobol. You actually could write "ADD VERMOUTH TO GIN GIVING MARTINI," which was the equivalent in any reasonable programming language of "martini = gin + vermouth."
PL1, by the way, was the first language I used to write a program -- at IBM when I attended their 360 introductory course. Not long after the IBM trip I attended a DOD seminar at the Pentagon entitled "Specifications for Selection" and learned that even though the 360 was in operation the government had never heard there was such a thing as multitasking.
And I always loved teaching. The only reason I didn't continue at CTU was that I was losing too much money per hour. CTU was paying something like $12 per classroom hour (didn't include preparation or grading) and I was charging as much as $100 / hr for designing and building software systems, which in those days was a bundle.