Preventative programming techniques provides programmers with a clear and intelligent approach to detecting, preventing, and correcting the most common mistakes. It includes practical ways to reduce problems that occur every day, and provides methods, for correcting problems that already exist. Using a medical metaphor, each of the common problems is presented as an illness. Each illness is then presented in a structured approach that includes a basic description, common symptoms, prevention methods cures, and related illnesses to look for. The majority of the principles and practices espoused are language independent and focus on instructing programmers how to detect and avoid problems. It also includes guidelines on determining when and how to refactor or rewrite code.Some of the major and minor illnesses found throughout programming, include premature optimization, cap (cut and paste) epidemic, NIH (not invented here) syndrome, complexification, oversimplification, docuphobia, and more. If you're a programmer, you've made these mistakes or you've had to deal with code that has them in it. To learn how to prevent and fix these problems, check out all of the illnesses? You're sure to find reading through each category of illness from start to finish, and experienced programmers will benefit from the insightful tips and anecdotes.Key features: provides insightful guidelines for avoiding common programming mistakes and writing cleaner, more efficient codeemphasizes early detection and resolution before the costs of problems explodecovers all problems from a non-language specific approach, providing examples in C++ and Java teachers practical guidelines for detecting what may seem like obvious mistakes that often go undetected until they cause serious problems includes a variety of tips and anecdotes that benefit all levels of programmers table of Contents: Part I: major illnesses1. Premature optimization 2. Cap epidemic 3. Nih syndrome part II: minor illnesses4. Complexification 5. Over Simplification 6. Docuphobia 7. I 8. Hardcode9. Brittle Bones10. Requirements Deficiency11. Myopia 12. Conclusionappendix a team work appendix B references appendix C about the cd-romabout author: Brian Hawkins (Los Angeles, CA) began his career doing research at just system pittsburgh research center where he focused on scripted character animation using natural language. He worked at Act I vision as the game core lead on star trek: Armada, and contributed to civilization: call to power and call to power 2. He also worked for seven studios as lead programmer on defender and now operates his own consulting company. He holds a BS in Mathematics and Computer Science from Carnegie Mellon University.