Part state of mind and part QA philosophy, the term "egoless programming" was coined by one of my favourite authors, Jerry Weinberg, back in 1971 in his highly influential book, The Psychology of Computer Programming. Weinberg was describing a development environment that involved heavy use of peer technical reviews. He used the term to describe the mindset that programmers developed after working in this environment for a time. The basic idea behind Weinberg's philosophy was that a system of formal peer reviews effectively multiplied the number of eyes looking for logic problems, poor algorithm choices, or even syntax. These extra eyes could catch nascent bugs much earlier in the development cycle than traditional testing could, resulting in shorter project completion times and lower defect counts in live systems. For developers to accept this system, of course, they had to set their egos aside. Popular peer reviewsDoes that sound familiar to you? It should. The idea of formal peer code reviews has figured in a number of development methodologies (or "fads," for the more jaded among our audience) and has been getting more popular recently. Extreme Programming, with its trademark two-developers-per-machine standard, could be viewed simply as a peer-review facilitation strategy. Likewise, the open-source community development process, which has historically been successful in producing high-quality, low-defect software, could be seen as one giant peer review. Obviously, thin-skinned developers (and some would argue there is no other kind) would be at a disadvantage when working in an environment where constructive criticism is handed out so freely. Programming, like writing or creating art, is a very personal endeavour, and, like artists, some of us just can't stomach it when someone else disparages our work. The Ten Commandments
What we need is a set of rules or guidelines to help developers keep themselves (their egos, actually) separate from their code. Hence our Ten Commandments for Egoless Programming, which you can also download in handy "stone tablet" format:
- 1.Understand and accept that you will make mistakes. The point is to find them early, before they make it into production. Fortunately, except for the few of us developing rocket guidance software at JPL, mistakes are rarely fatal in our industry, so we can, and should, learn, laugh, and move on.
- 2.You are not your code. Remember that the entire point of a review is to find problems, and problems will be found. Don't take it personally when one is uncovered.
- 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.
- 4.Don't rewrite code without consultation. There's a fine line between "fixing code" and "rewriting code." Know the difference, and pursue stylistic changes within the framework of a code review, not as a lone enforcer.
- 5.Treat people who know less than you with respect, deference, and patience. Nontechnical people who deal with developers on a regular basis almost universally hold the opinion that we are prima donnas at best and crybabies at worst. Don't reinforce this stereotype with anger and impatience.
- 6.The only constant in the world is change. Be open to it and accept it with a smile. Look at each change to your requirements, platform, or tool as a new challenge, not as some serious inconvenience to be fought.
- 7.The only true authority stems from knowledge, not from position. Knowledge engenders authority, and authority engenders respect -- so if you want respect in an egoless environment, cultivate knowledge.
- 8.Fight for what you believe, but gracefully accept defeat. Understand that sometimes your ideas will be overruled. Even if you do turn out to be right, don't take revenge or say, "I told you so" more than a few times at most, and don't make your dearly departed idea a martyr or rallying cry.
- 9.Don't be "the guy in the room." Don't be the guy coding in the dark office emerging only to buy cola. The guy in the room is out of touch, out of sight, and out of control and has no place in an open, collaborative environment.
- 10.Critique code instead of people -- be kind to the coder, not to the code. As much as possible, make all of your comments positive and oriented to improving the code. Relate comments to local standards, program specs, increased performance, etc.
For all job and work-related news, or to search for a job and get information on training, go to ZDNet Jobs.
If you have something to say about work and employment issues say it here at the Jobs Forum.
Let the editors know what you think in the Mailroom.
