| Nice post, but just a little too much corporatespeak for me. My take: 1. Be an egoless programmer. I've heard this a million times and always hated it. I lost count of the number of projects I've witnessed that were saved when someone who knew what they were doing put their ego on hold. You know what you're talking about: you have a moral responsibility to speak up and do the right thing, ego or not. I prefer, "Don't be bashful but be nice." 2. Be a team player. Oy, this sounds like something my PHB would say. I prefer, "Just do your fucking job." 3. Be a learner. Absolutely! But don't restrict your learning to technology. Learn about your customers' and users' domains. Suffer with them and their problems. You'll probably get far more milage out of that than more technology. 4. Be a T-shaped person. I like this, but again, I would add my customers' domain. Being the go-to person with deep understanding of the technology who knows how to apply it to the problem at hand is a deadly combination. 5. Be relentlessly resourceful. What does this even mean? I prefer, "The answer is always 'yes'. Sometimes, 'yes but', but always 'yes'". |
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.