Pattern Recognition #9: The Template Method Pattern

(Gemini generated)

Hey there! Welcome back to our design patterns journey. In the last article, we explored the Facade Pattern — simplifying complex subsystems. Today, we’re diving into another behavioral pattern — the Template Method Pattern.

If you’re not a Medium member, you can still read the full article by following this friend link here. I hope you enjoy it :)

But before we jump into theory, let me ask you: Have you ever implemented the same workflow in multiple classes with just 1–2 steps different? Like:

• processing different file formats (CSV or JSON)
• different payment flows (card vs UPI)
• different beverage recipes (coffee vs tea)

If yes, you’ve likely duplicated code and then suffered when requirements changed.

The Template Method Pattern fixes this by placing the algorithm skeleton in one place (the superclass), while letting subclasses fill in the details.

The Problem: Barista Training Manual

Suppose you’re implementing the internal “barista training” system for some XYZ Coffee.

They give you two recipes:

• Coffee: Boil water, brew coffee in boiling water, pour into cup, and add sugar and…