Pros and cons

Using third-party code is not always the best way to go (that is, assuming that you have found third-party code that meets your requirements), but rejecting it outright is similarly unwise.

The decision ultimately rests with whatever combination of requirements, timelines, developers, managers, and clients is involved in a project (as well as all of those who have been involved on the project in the past, if that's the case).

But let's take a look at both sides of the scales.

The case for third - party code

There are very good reasons to use third-party code. Some very good developers do it all the time, and most do it often. So here are some reasons to resist the temptation to announce proudly I don't use third-party code on principle...