In my previous post, I looked at some of the problems associated with long parameters lists for methods and constructors. In that post, I discussed replacing primitives and built-in types with ...

In my two immediately previous posts, I looked at reducing the number of parameters required for a constructor or method invocation via custom types and parameter objects. In this post, I look at ...

Reference objects aren't just useful when memory is at a premium; they can also be used to provide slick caching abilities to any application.

Is it poor programming practice to pass parameters as objects? Are you making code more maintainable? Or just covering up poorly defined methods?