9 Third-party libraries: Libraries you use become your code
This chapter covers
- Taking responsibility for the libraries you import
- Analyzing third-party libraries for testability, stability, and scalability
- Making decisions about reimplementing logic vs. importing code you don’t own
When building our software systems, we have time and budget limitations. Because of those limitations, it is not feasible to write every piece of code that your software uses. Almost every application needs to interact with the underlying operating system, filesystem, and external I/O. For those interactions, we usually don’t reimplement the logic. We pick the libraries that are already present and provide that functionality for us. We call those libraries third ...
Get Software Mistakes and Tradeoffs now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
