Skip to main content

Lists or Objects

"Our rule of thumb is that we try to limit passing around types with generics (the types closed in angle brackets). Particularly when applied to collections, we view it as a form of duplication. It's a hint that there's a domain concept that should be extracted into a type." Growing Object-Oriented Software, Guided by Tests - Steve Freeman, Nat Pryce, page 136)


Not ideal - business logic will leak.

Better - quotes are now encapsulated.


The benefit of the second approach is that you begin to force the collection to do the work. Consider a collection of quotes - using the first approach a developers' typical instinct would be to loop over the list and check each quote until the lowest quote was found. You could argue that this in turn violates the 'Tell Don't Ask' principle because very quickly you can find yourself digging down into objects. We would not do this with standalone objects, so collections should not be any different. Yet as developers we often avoid creating objects to encapsulate collections, despite this principle being taught in the early chapters of any OO programming beginners book.

Another key point of encapsulating collections is that you reduce duplication. If another part of the application needs to perform a check for the lowest quote, you'd end up either duplicating the code to loop over the quotes, or creating a helper method to do the actual processing. Using the collection means such features are only a method call away at all times.

In a recent code kata as well as a current set of work, we are applying some of the above concepts and finding a dramatic increase in the quality of our code. Those of you may have noticed that the above implementation inherits from a standard list, therefore it is indeed possible to still violate encapsulation and dig through the collection yourself. There are pros and cons to this approach, one benefit is all of the out of the box functionality you get for free - the ability to loop over the quotes (for displaying say) and return a count for example. The downside being developers can treat these collections as if they were a list.

In C# it is possible to use indexers or interfaces to improve the above implementation, though we tend to agree that it's up to the developers to do the "right" thing - in other words, not dive down into the collection. Interesting this very topic has been discussed on the excellent StackOverflow - I and others will sure agree that the answer(s) provided are well off the mark. Encapsulate your public collections - do not treat them as primitives!


Popular posts from this blog

Constant Object Anti Pattern

Most constants are used to remove magic numbers or variables that lack context. A classic example would be code littered with the number 7. What does this refer to exactly? If this was replaced with DaysInWeek or similar, much clarity is provided. You can determine that code performing offsets would be adding days, rather than a mysterious number seven.Sadly a common pattern which uses constants is the use of a single constant file or object. The beauty of constants is clarity, and the obvious fact such variables are fixed. When a constant container is used, constants are simply lumped together. These can grow in size and often become a dumping ground for all values within the application.A disadvantage of this pattern is the actual value is hidden. While a friendly variable name is great, there will come a time where you will want to know the actual value. This forces you to navigate, if only to peek at the value within the constant object. A solution is to simple perform a refactor …

Three Steps to Code Quality via TDD

Common complaints and problems that I've both encountered and hear other developers raise when it comes to the practice of Test Driven Development are: Impossible to refactor without all the tests breakingMinor changes require hours of changes to test codeTest setup is huge, slow to write and difficult to understandThe use of test doubles (mocks, stubs and fakes is confusing)Over the next three posts I will demonstrate three easy steps that can resolve the problems above. In turn this will allow developers to gain one of the benefits that TDD promises - the ability to refactor your code mercifully in order to improve code quality.StepsStop Making Everything PublicLimit the Amount of Dependencies you Use A Unit is Not Always a Method or ClassCode quality is a tricky subject and highly subjective, however if you follow the three guidelines above you should have the ability to radically change implementation details and therefore improve code quality when needed.

DRY vs DAMP in Tests

In the previous post I mentioned that duplication in tests is not always bad. Sometimes duplication becomes a problem. Tests can become large or virtually identically excluding a few lines. Changes to these tests can take a while and increase the maintenance overhead. At this point, DRY violations need to be resolved.SolutionsTest HelpersA common solution is to extract common functionality into setup methods or other helper utilities. While this will remove and reduce duplication this can make tests a bit harder to read as the test is now split amongst unrelated components. There is a limit to how useful such extractions can help as each test may need to do something slightly differently.DAMP - Descriptive and Meaningful PhrasesDescriptive and Meaningful Phrases is the alter ego of DRY. DAMP tests often use the builder pattern to construct the System Under Test. This allows calls to be chained in a fluent API style, similar to the Page Object Pattern. Internally the implementation wil…