A UI designer does a good job if the person who's paying them thinks they did a good job, not whether or not they actually followed best practices, unless that's how the work gets approved. A frontend developer does a good job if their tickets are done and their boss likes them, which may or may not include actual quality work that's accessible or usable. That's the secret I wish I'd known when I started working, could have avoided the extra personal cost of trying produce quality results despite there being no incentive structure for it.
Just like morality and law are not the same, the objective quality of a UI designer's work doesn't necessarily have anything in common with their employer's preferences.
You're right that only one of those is paid well, but that's not what GP was talking about.
> You're right that only one of those is paid well, but that's not what GP was talking about.
I didn't say anything about how much someone is paid, just that it is often a job, and whether you have a job depends overwhelmingly on whether the person paying you is convinced that you're doing it well, which may or may not relate to the objective merit of the work. It doesn't matter if you're making $150k or $20k, but it's not wise to prioritize things that nobody paying you didn't ask for.
The exceptions are of course things that don't pay at all, in which case your goal is still probably to get the best job you can done under the constraints provided. If those are too tight, things get cut, or you don't sign up for it.
