[hga]

The concept of the egoless programmer, which this article is using correctly, is an old one, introduced by Jerry Weinberg in his 1971 The Psychology of Computer Programming (read it if you haven't, it's still very relevant even if we're not using punched cards anymore). Wikipedia describes it pretty well, and also notes it was in opposition to the then trendy "chief programmer" model (which I'll note was in part a response to computer time being very very expensive back then): http://en.wikipedia.org/wiki/Egoless_programming

I think you might be misreading it, it's all about both speaking up and accepting criticism; let me just repeat what the article says:

"Remember that you are not your code. The only way to improve is to be open to feedback from others and give honest, non-judgemental feedback to others."

What's bad about any of that?

And while I haven't followed the "rockstar" programmer concept, the connotations of "rockstar" certainly would seem to include an unproductive amount of ego.