In this post I discuss the benefits of using library wrappers. Part 2 discusses testing and linting of the same. The examples will use Ruby, but the ideas are more broadly applicable. When I wanted to update the AWS gem used by a large Ruby codebase, I found that there were many breaking changes in the target version. Worse, usage was scattered among hundreds of files, and varied from case to case. There were few easy find-and-replace fixes; instead, usage would have to be edited by hand to conform to the new APIs. ...