I wasn't 20 years into my career when I did this (more like 10), but at one point I had a serious "lapse of faith" with regard to my career. I was working for a terrible company with an even worse manager and I was miserable. I didn't know if I wanted to be a programmer any more. I quit my job and didn't look for another one. Instead, I wrote free software -- initially just for a month. I got up in the morning, had a…
So many things were developed in the late 1990's and early 2000's that indeed were hairy and tricky to use; and as a fresh developer I too hated much of it and tried to avoid them. So in that sense I was part of the problem. But now that I have some years of experience, I can't help but feel that we do so much things in ways that were solved 20 years ago, just because the newcomers in the field don't understand or can't be bothered to learn the history and why things are the way they are - and the whole 'simple framework of the months' cycle keeps going.
I guess this topic is relevant to the discussion after all - I think much (at least some) of our burnout is because of this never ending cycle of 'new' for the sake of new, yet seldom really better than what we had before. But maybe it's just rose colored glasses, and things now really are better...