I feel for you, I hope that one day we can escape from CMS hell (at least now I'm not doing content on one).
The firing isn't so bad if its from the right place. The company had a big layoff that coincided and I just say that I was part of that, but really people don't pry too much, and its a company that consistently burns people out anyways so no one really bats an eye. Honestly I thought it'd be way worse, but it really isn't that bad.
Well, I was with what was more of a temp agency than someone as mercenary as the guy you worked with, but man if that isn't the dream to get to that point someday. I just worry that you end up spending a lot of energy worrying about what your next gig is going to be in your off time if you don't set it up right. The other worry is being the sort of person it takes to deliver a product in the kind of timespans and constraints contractors like that work on, it'd be so nice, but I just don't know if I'm that kind of person after the jobs I've worked.
I'm glad that you were able to take off some of that stress, I totally feel the same way about how much effort it is just to get going with work, especially when everyone wants to take up time with meetings.. Time is going way too fast lately, especially when everything seems like its the same.
My personal issues landed about as well as they could have, but I can feel the encroachment of burnout in myself, I think I really need some time away too. I hope you're doing what you can to bear with things.>>21
It really depends on the company, but I see a lot of (smarter) places having a built-in expiration date for code so it doesn't end up being too legacy in newer companies. Patterns like microservices let you cut your losses and slot in something new with less pain that looking at a massive decade(s)-old codebase that no one on the team ever fully understood. Of course, I know some people that are in the public sector that are working on code older than their parents, so it goes both ways.