2011 July : Dragons in the Algorithm

Archives

When to Wrap a Library

I find that this comes up fairly frequently. You find some useful library: perhaps it does logging, or enforces design-by-contract, or it provides an API for calling web services. But someone on the team suggests that instead of using the library directly, we should create a wrapper: “that way, if we ever decide to switch to a different library instead it will be easy to switch”. Is this a good idea? more…

[Here there should be links to more entries, but WordPress is a pain and I can't make it work.]