The Moment
You’re watching a movie. The hero makes a choice. You know what happens next - not because you’ve seen this movie, but because you’ve seen this pattern.
The mentor dies. The hero doubts. The comeback begins.
Same pattern, different story.
Here’s the thing though: once you see it, you can’t unsee it. It’s always the MacGuffin. Now you spot it in every movie, whether you want to or not.
If you are not familiar with a MacGuffin, stay innocent. Some patterns are better unseen.
The Same Eyes, Different World
At work, I build systems. I see the same things appearing over and over:
- A problem that needs solving in three places
- A solution that could work for all three
- An abstraction that makes the next problem easier
Twenty years ago, I noticed something about data integrations. Same structure, different data. That pattern became my default design approach — still is, refined but fundamentally unchanged.
Software isn’t special; it’s just a digital version of a movie script. What looked like complexity became clarity.
What Patterns Do
This is for anyone who builds things — code, systems, habits.
Patterns do three things:
- They simplify - One idea, many uses
- They connect - Same root, different branches
- They predict - Recognize the shape, anticipate the next move
Where Patterns Hide
Patterns show up everywhere:
- In movies: the reluctant hero, the false victory, the final test
- In grocery stores: the layout, how snacks are close to checkout
- In code: the same solution solving different problems
- In conversations: the same friction points, the same breakthroughs
- In organizations: the same bottlenecks, the same fixes
Different domains. Same shapes.
The Trap
Not every repetition is a pattern. Sometimes it’s just the same thing happening again. Phil Connors in Groundhog Day lives the same day over and over until he learns the pattern: change yourself, not the world around you. Same with Cage in Edge of Tomorrow — die, learn, adapt, respawn. The loop isn’t the trap; refusing to change is. Both characters escape when they realize the pattern isn’t about repeating the same actions. It’s about iterating toward something different. Real patterns adapt. Fake patterns just loop.
A real pattern:
- Works across different situations
- Makes the next problem easier
- Survives when details change
A fake pattern:
- Only works in one specific case
- Creates complexity instead of reducing it
- Feels clever but doesn’t help
Why It Matters
Pattern recognition isn’t just for engineers.
- A manager sees the same team dynamics across projects
- A parent sees the same conflict pattern with their kids
- A writer sees the same story beats in different genres
Once you recognize a pattern, you can name it. Once you name it, you can use it.
The Takeaway
“I see patterns” isn’t about complexity. It’s about clarity.
When you spot something working — a conversation style, a code structure, a habit — ask: what else does this fit? Then try it. That’s the whole method.
The Future Layer (For the Curious)
We are moving into a world where AI can help you do the work in 100 different ways.
In this world, “doing” is cheap. Recognizing what needs to be done is expensive.
When you see a recurring success and name it, you aren’t just observing. You are modeling a process. Whether you’re teaching a child a habit or teaching an AI a new capability—the process is the same:
- Find the pattern.
- Name the pattern.
- Turn the pattern into a repeatable process.
Identification is a new form of creation.
Disclaimer: Of course, life, code and AI are more complex than this post makes them sound. I’m stripping away the jargon to get to the core. If you’re more familiar with the topic, you know there’s a much deeper “rabbit hole” beneath this—but that’s a story for another day.
The engineer sees abstraction. The storyteller sees structure. The parent sees dynamics. All patterns. All the same skill, different lenses.