Compendious Thunks

Swap a list for map in the Composite -- is it no big deal? Or did you just make a… Composite Tommyknocker?! compendiousthunks.com/series…

We use the Composite Pattern b/c it's easy -- to use and grow. The consequences, they are joy! compendiousthunks.com/series…

Just how much should component and composite share in the Composite Pattern? Spoiler: nearly everything! compendiousthunks.com/series…

In the composite pattern, a collection-like composite is how you build and maintain beautiful, complex composites: compendiousthunks.com/series…

Stay sane when building composites of composites of composites (and even more complex things!): compendiousthunks.com/series…

Control one or many objects — w/ identical operations! It's the freebie Introduction to the Composite Pattern: compendiousthunks.com/series…

Just because you *can* share flyweight objects doesn't you _have_ to. Let's talk Unshared Flyweights: compendiousthunks.com/series…

Sharing a simple data structure up-front might make communication issues in the Flyweight Pattern obsolete: compendiousthunks.com/series…

Another thunk! Today, we're keeping the information flow in the Flyweight sane, thx to a simple convention: compendiousthunks.com/series…

The flyweight is pretty… fly (ahem). But communication equals complexity. Also, what the heck is extrinsic? compendiousthunks.com/series…

Visitors are beautiful. And their beauty can blind us when they get a little… too familiar w/ our objects: compendiousthunks.com/series…

Oh, no!! It's a PATTERN BATTLE! Don't you dare look away from… Visitor vs Iterator! compendiousthunks.com/series…. And, yup, it's the #fightOf2017

Never add new object types to be visited in the Visitor Pattern. But when you do, here are some handy tips: compendiousthunks.com/series…

Add 4 new operations and perform major refactoring in 5 minutes. Impossible? Not for the Visitor Pattern compendiousthunks.com/series…