>Skilled programmers recognize what makes good code good, and what makes bad code bad You're still somewhat biased, so you can get put on projects where the st

>Skilled programmers recognize what makes good code good, and what makes bad code bad You're still somewhat biased, so you can get put on projects where the style is different from yours. If you happen to think that style is bad, it won't be fun to work on. You shouldn't want to change the style. Chances are you'll do it incompletely (job change) or the time spent won't be worth it. If someone else comes along and doesn't like your style, we're just going to repeat this process. There's been way too many different approaches that work for developers to be unified on what styles are best.