Ah legacy enterprise software/hardware, it keeps me employed and insane. Where i currently work we have a system which was originally designed in '69(coding started in 75) running on an ibm iSeries. It's old old tech and most of the system is cludged together so poorly that instead of being able to write patches we just write wrappers around the applications(micro services really) that modify the program as its runni…
I know of someone who is in the position of your snowbird, though still employed. He almost delights in the fact that there's been no effort to upgrade from something completely reliant on him, even though he knows the situation is crazy. And he has no personal interest in writing himself out of a job. I can't approve of that attitude.
Why not?
Most companies that end up with that kind of hardcore legacy code a) refuse to upgrade on a reasonable basis and b) refuse to compensate their developers in proportion to the value they ultimately deliver.
So, fuck'em. Might as well enjoy the pseudo pension.