and listening to the entire internet say "if you don't like one tiny aspect of your work environment, its a huge red flag for a bunch of other stuff so just leave!" as if such choice in the matter is really there and that the next organization doesn't have some other tiny cringy thing
so then if you ignore that advice, you're stuck with the childish babble that the people in your organization use to cope
A teammate once told me he is frustrated with being asked to work on an MVP, that is minimum cost, minimum polish, minimally functioning. He said he wanted to work on MLP, so I said he can call it MLP if he wants, but what we must build does not change: prove the concept minimally such that we can verify whether the problem we seek to solve is a real problem in the first place, then we can add as much polish as needed once we know it's a good problem to solve. If we think customers are experiencing some problem that, in order to solve minimally, we need to give them polish, then the polish is a part of the MVP/MLP. Otherwise, it is not. It doesn't matter what we call it. What matters is what we must do.
He thought that my attitude taking the distinction between MLP and MVP lightly was a sign that I do not care about the best interest of our customers, and left the company.