3 ms·

> I've learned to appreciate my job for what it is, and for the benefits that it provides in comparison to other jobs that I could easily obtain. This is what

> I've learned to appreciate my job for what it is, and for the benefits that it provides in comparison to other jobs that I could easily obtain. This is what it boils down to, imo. Currently I'm working on a horrendous legacy code base with a very low performing team, in a very low performing organization. Over the years I've learned what matters to me, and this job has what I need: good pay, time off, and I can come and go as I please so long as I'm here for "core" hours (ie on location, not remote). The last part is another way to say my boss is cool. He's new too, although he's been here longer than I have. We're both dismayed at the do nothing culture, and terrible code here. That's about all anyone can ask for IME, find out what matters to you and optimize for that. When I go home I don't give a thought for work, I get to concentrate on my family 100%.

gwbas1c 9y ago
> > I've learned to appreciate my job for what it is, and for the benefits that it provides in comparison to other jobs that I could easily obtain. Part of why it works out so well for me is that I have enough clout to avoid things I don't want to do. IE, I don't want to be a manager. When my manager, (who's titled a director,) decided that I was going to become a manager, it basically went like this: Me: "I don't want to be a manager." My boss, "You're not going to be a manager, you're just going to do [everything that a manager does]. You need to grow in your career." Me: "That sounds like you want me to be a manager." I saw right through that and made it pretty clear that I wasn't going to be a manager, and I wasn't going to be tricked into being a manager without the title of manager. If I was going to be forced to be a manager, I was going to take that job I mentioned in my original post. It helped that I missed a meeting with upper management because a job interview ran long. In part, it's not that I don't want to be a manager, I don't want to be a manager for the company I work for. I know too much of the code to be hands-off, and I'm remote. The culture is far too interrupt-driven in our office to be a remote manager.

gwbas1c 9y ago

> > I've learned to appreciate my job for what it is, and for the benefits that it provides in comparison to other jobs that I could easily obtain. Part of why it works out so well for me is that I have enough clout to avoid things I don't want to do. IE, I don't want to be a manager. When my manager, (who's titled a director,) decided that I was going to become a manager, it basically went like this: Me: "I don't want to be a manager." My boss, "You're not going to be a manager, you're just going to do [everything that a manager does]. You need to grow in your career." Me: "That sounds like you want me to be a manager." I saw right through that and made it pretty clear that I wasn't going to be a manager, and I wasn't going to be tricked into being a manager without the title of manager. If I was going to be forced to be a manager, I was going to take that job I mentioned in my original post. It helped that I missed a meeting with upper management because a job interview ran long. In part, it's not that I don't want to be a manager, I don't want to be a manager for the company I work for. I know too much of the code to be hands-off, and I'm remote. The culture is far too interrupt-driven in our office to be a remote manager.