Description
It's generally better to use libraries than to write your own code, but what happens when you run into an issue that is correctly solved by modifying the library code rather than your own code? What if you need to deploy a fix today, but you can't count on the upstream library applying the required fixes and getting a new release through your deployment system before your deadline? This presentation will cover various stop-gap strategies (of varying desirability) for dealing with this situation, including:
- Working around the bug with wrapper functions
- Monkey patching the offending methods or functions
- Vendoring a patched version of the library into your application
- Maintaining a forked version in your local package manager