Home / consequences
Composite Easiness
chris | 4 April

The Composite Pattern makes for all kinds of easy in code. But as code evolves, guard against veering from the

Read More
Maximum Composite
chris | 20 March

How much should composite and component share? Pretty much everything, it turns out. Just watch out for some potential consequences

Read More
Composite Hierarchies
chris | 18 February

Composing is built into the Composite Pattern name. But it goes a bit beyond composing simple composites of composites. We

Read More
When Visitors Get Too Friendly
chris | 10 January

Friends are amazing. They’re a good thing in code too. But it’s easy to get too much of a good

Read More
Visitor vs Iterator!
chris | 6 January

At first blush, it might seem like an iterator can solve the same problem that the Visitor Pattern solves. But

Read More
Non-Delivery in the Chain of Responsibility
chris | 8 November

What happens when a request reaches the end of the successor chain? Does it get lost in the ether? Should

Read More