nah, this is just the brilliant hacker type mentality (individual over team, parachute in and rewrite everything in today's cool language) type stuff that gets really annoying once you're responsible for a set of interconnected components of software that matter.

it's critical to root out these hero types lest they ruin your organization with hand grenades wrapped up as "refactored" projects using the latest language. seniors won't put up with this, and rightfully so: it basically raises a middle finger to the organization's previous culture/work, and they are now responsible for doing it... again. it's disrepectful and ought to be a fireable offense, ideally rooted out in the first few weeks when the new team member is given some slightly autonomous tasks.