I've had the pleasure of working with a developer who strongly believes that all classes external to your assembly (even core framework classes) should be wrapped in an internal class. The idea goes something like this. If your external class ever changes and the author decides to make it not backwards compatable ... and the new version of the class is actually required, you only have to change your wrapper class once instead of having to do a global search and replace.

Fair Enough. Reader Vijay's colleague employs this concept full throttle:

Remember. Hey, you never know when the implementation of the Integer DataType will change. But when it does, Vijay's colleague will be safe.

Don't forget to send in your WTF-Moments. Doesn't have to be code-snippets or diagrams. Just whatever you think like-minded techies would enjoy!

[Advertisement] BuildMaster allows you to create a self-service release management platform that allows different teams to manage their applications. Explore how!