Perhaps a disclaimer first, I haven’t found this in textbook, although I wouldn’t be surprised if it were. It’s actually an explanation I used on a job to explain how splitting responsibilities would help them in their DTAP environment. It’s a loosely defined way of looking at some responsibilities of some facets with respect to testing and deployment. ...
There seem to be a significant amount of Java developers who have certain criticisms to the Java approach of implementing Generics. Though type information is sometimes well hidden, it's almost always available. This is because of the approach that Sun took when defining it. Sun decided that it was not appropriate to compile new types just because the type information itself changed. This approach differs from the C++ template approach which requires the original sources of the generic class you're using, this makes it very hard to provide a generic class in a library. ...
When building utility classes, testing becomes more important than in other parts of the software. Utilities are hopefully (re)used a lot and thus should have the most reliable behavior. This also means that documentation should always be up to date. Though utilities are generally easy, they might not be the easiest to test. I created a little example of a utility that I often use, depending on the application, often bearing the name "SettingsUtil". It's a simple class that returns properties from a property file somewhere on the classpath and returns either the value for a specified key from the properties file or a default value if no value is associated with the given key. ...
