Chapter 3: NIH Syndrome

---

 Download CD Content

Description

Many programmers are opposed to using code other than their own. However, while there are reasons to be wary, it does not mean that you should refuse to trust any third-party code. Unfortunately, this seems to be the most common mindset when it comes to using external code. If the code was Not-Invented-Here, which can mean anything from within the company to an individual level, then it cannot be good enough for the task at hand. Some of this comes from legitimately bad experiences, but most of the time it is more inherent in the way the programmer thinks. This type of thinking is extremely problematic for software development, and as the complexity of software increases it will only become more so. It is imperative that something be done to curb this trend of rewriting code for every project at every company.

Fortunately, there are ways to improve the use of third-party code that will ease the mind of the paranoid programmer. By adopting these practices, you both remove the psychological barriers to using other’s code and reduce the real risks in doing so. You can also demonstrate to other participants how the risk is minimized to convince them that using the third-party code will not bring the project crashing down.

---