Check out this list from Coding Horror. With just one or two exceptions, it could just as well be the Ten Commandments for how to be an egoless employee or boss, or even an egoless human being. Certainly, anyone who does work that requires interdependence with others would benefit from following most or all of these rules. I especially like #3:
'No matter how much "karate" you know, someone else will always know more. Such an individual can teach you some new moves if you ask. Seek and accept input from others, especially when you think it's not needed.'
That last sentence is really something. Think of how much human misery would have been averted if more leaders and so-called experts of all stripes had sought input especially when they thought they didn't need it.
Thanks for a great pointer, Bob.
Posted by: Wally Bock | July 07, 2008 at 04:00 PM
Thanks for this link. I am going to share it with the people I work with.
Since much of my work involves software testing, a big part of my work is identifying incorrect code. Some developers instinctively dread feedback from testers, and some welcome feedback.
One of the first things that I tell any developers that I work with is that my job is to make them look good. I emphasize that I assume that all of them are good developers and that I will not judge them. If I find an error, they should be happy because that means that an end user, a manager, or a project sponsor did not find the error. I emphasize that we're a team that all has the same goal of delivering a quality product to the end users.
This little chat seems to bring around most developers who I work with to a positive and collaborative point of view.
Posted by: Kevin Rutkowski | July 04, 2008 at 07:44 AM
A good guide, thanks. Something very interesting and unknown!
Posted by: amosgitai | July 03, 2008 at 02:47 PM