You have to be careful what you're good at. If senior devs/management sees you're good at legacy, they might task you with that as a majority of your time. Then your career plans get sidetracked because you won't have as much time working on the stuff that you want to work on.
Some developers are okay with legacy, but if they aren't, it's not surprising. Some legacy stuff is absolutely horrible to work with - it devolves into "get-in-get-out" fix mentality (and security issues usually get swept under the rug). Some legacy products are good though and require minimal tribal knowledge to actually work on.
This has happened to me twice at two separate positions: bait-and-switches about what I'll be working on because more senior members wanted to offload the legacy work themselves.
The general arrogance is really a separate trait from willingness to work on legacy IMHO and I agree on those points.
I worked at a company that did this. Eventually customers start demanding stability as a feature. There is a huge difference between arrogance and wisdom.
Ummm... are you sure, THEY are the arrogant ones?
I'm sensing some irony here.
If a business is treated like that, maybe it should quit its current development team and try to get a job at another.
Businesses loose millions and they just burn cash because of toxic and arrogant developments teams.
I can quadruple the sales of the company that I work for but you cannot push any change through the arrogant development team who don't give a chance to other people, it is so pathetic.