As Steve’s book states, classic mistakes are classic mistakes because they’re mistakes that are made so often and by so many people. They have predictably bad results and, when you know them, they stick out like a sore thumb. Half the battle in shipping quality software is avoiding making mistakes - something that is easier said than done. The other half of the battle is using efficient development practices that ensure well written, thought-out, designed and tested code.
The idea behind listing them here is that, once you know them, you can spot them and hopefully do something to remedy their effect.
Classic mistakes can be divided in to four types:
- People Related Mistakes
- Process Related Mistakes
- Product Related Mistakes
- Technology Related Mistakes
Today’s blog takes a quick look at the first of Steve’s categories of mistakes: People Related Mistakes.
Undermined MotivationAvoid doing things that undermine the motivation of other members of your team.
Weak PersonnelHire the best people you can find. Never hire from the bottom of the barrel.
Uncontrolled Problem EmployeesNot sacking problem employees results in lower motivation for the rest of the team and the reworking of their areas of code.
HeroicsAllowing heroic gung-ho developers is similar to putting a bull in a china shop. Gung-ho heroics threaten the schedule because slips aren’t detected until its too late. Some managers praise heroic developers working all hours battling away to get a project completed on time.
Isn’t it better to have steady, consistent 9 to 5 working and progress reporting. Get a life. If you have to work heroically then project is in big trouble.