Link Details

The other day, I was reviewing a coworker's design for an area she was writing. As she was describing the responsibilities of each class, my attention was drawn to one in particular: "Why is this method in this class Foo? I mean, it's true that the operation does have something to do with Foo objects in general. But isn't a really specific method, one you'd expect the user of this object to be doing? It's a bit if you were to have this really app-specific string manipulation function, and then throwing it into the global string class even though no one else would ever need it".