An idea I have thought about is having a culture of individual demos. Being put on the spot sucks, but taking responsibility and pride in your work is an important step to encouraging those who do to grow and shine, and forcing those who don't out of the shadows. Demos do not necessarily have to be presentations on stage under a spotlight - they can be of any format including videos, drawings, research papers, or distributed software.
For this to work though, the demos cannot just be some adjunct ritual to the organization's "real work", with the sole purpose of name and shame. The demos must be the byproduct of your entire work in the organization. What sprouts from the individual demos, may lead to improvised teams for larger projects, but the demos are always the driving force, there to empower the individual and their ideas.
Have you heard of any organizations that implement something like this?
The idea is influenced by various stories I have heard over the years about Valve, Pixar, and Apple. Not sure if any company currently implements such a system.
Typical flow handled by one person is about 3 weeks from start of coding to live code, and then a couple more weeks on followup, stats, bugs, etc. After that it's just part of the codebase and others can end up working on it; but they'd probably talk to the original author to get up to speed.
A way in which those people are extremely dangerous if the organization allows them to thrive with such a behavior is that smart, productive employees will realize early on what's happening, and will follow suit in order to not fall behind. Entire teams can get poisoned in 6-12 months just like that.
If your company is a fucked-up hellhole, there are people whose responsibility this actually is.
You have to remember if the person is thoroughly incompetent, none of this will work, but imagine if the person is actually pretty smart and good enough to get by, then make them personable and friendly ... and throw in a manager who doesn't really know shit about what you do ... then its a whole new ball game. In fact someone like this could wind up getting promoted over you into a "architect" role or some quasi-dev manager role (bosses who don't really know what developers do, love over communicators). I've seen it happen.
Often times, they can gather a mob (depending on their social skills) and push out other engineers they don't like, or completely comandeer the engineering organization into ill-fated directions.
What I'd like to hear from the OP is ways to counteract this kind of behavior, I suspect there might not be a way to do it if you're a peer, only if you're that person's boss.