[capableweb]

It's always easier to drop everything and find better pastures when shit gets hard and/or bad.

But is it best for your long-term growth? If you're already in a difficult place mentally, it probably is best to leave. But if you're in a good place generally, and up for a challenge, you learn a ton more when you go from hard/bad to easy/good, and those skills are very sought after in the market place.

So if you can gain those skills, I'd go for doing just that. But again, that's not for everyone.

[wheybags]

Framed another way: is it better for your long term growth to work with colleagues who can teach you new skills, or to try to wrangle a dysfunctional team?

IMO it depends on what you want to learn. If you want to develop your technical skills, it's definitely good to go somewhere that you're not the best dev in the room. Wrangling a team is more management / soft skills.

[capableweb]

> is it better for your long term growth to work with colleagues who can teach you new skills, or to try to wrangle a dysfunctional team?

Good point, although I'd consider "wrangle a dysfunctional team" as a skill, granted the team is only dysfunctional because of good management, not if they are inherently bad programmers, too big egos or whatever.

> IMO it depends on what you want to learn

Yeah, that's a good point. That nuance in my comment was missing to thanks for adding that.

[toqti]

Thank you, I am being as positive as I can!

[spacemanmatt]

I can tell, and this is a familiar situation to me. It's hard to remember what a good environment is like when you have been exposed to dysfunction for a long time. I advocate good organizational health, and I can't do that independently if I stay in bad organizations for too long.