This question already has an answer here:
My team and I develop and application which uses a number of third-party libraries to fulfill certain common functions. (It's a Java application and uses a number of Apache Commons libs, Log4j, etc.)
I have been asked to justify the use of third-party libs as opposed to coding everything in-house. I have explained that it is standard practice in software development, that it reduces the need to write and test our own code, and that the libs' long history and "many eyeballs" mean that library code is likely to be more reliable than our own.
My explanation is all well and good (IMHO!) but is there a more formal explanation of why using third-party libs is generally good practice — in a book, or a web page by a respected developer, for example?
(Edit: Unlike the question marked as duplicate, I'm not after a bunch of opinions. I'm specifically after a well-respected source I can cite to back up the prevailing opinion. However, I've just been pointed at the FAQ which explains that asking for off-site resources isn't allowed, so apologies for posting this question.)