I've worked with folks like the ones he cites. I've been jealous of their ability to absorb new things, but then you realize they're absolutely allergic to any kind of maintenance or responsibilities beyond "build, build, build".

There's a difference between introducing new things because they are a well thought out appropriate choice and completely ignoring the standards of the company because you want to do resume driven development. I believe the author is talking about the latter.

The point is that developers like this purposefully introduce new languages and frameworks that only they (and maybe not even they) fully understand, so they make themselves harder to replace and ensure that they appear ahead of the curve. (Then they get bored and leave anyway.) It's totally valid to introduce new technologies when the problem calls for them, but doing it in a way that's purely detrimental to the rest of the team is very selfish.

Just look at the author's accolades. They are very light.

I've never heard of this guy. He's "self employed"

The article lacks any real detail and it just a guy patting himself on the back.