Why I Started Pattern Engine
Old wisdom, modern systems, and the patterns that run underneath both.
I keep running into the same problem from two directions.
At work, I build AI systems for the internal operations of a national healthcare enterprise. RAG pipelines, MCP integrations, agentic automation — tools that help our teams move faster and make better decisions. Outside of work, I build products and systems for people solving fuzzy, high-stakes problems with these same pattern machines. The technical challenges are hard, but solvable. The harder question is what these systems do to the people using them: how they reshape attention, affect judgment, create dependencies that nobody asked for and nobody fully understands.
Then I go online and find the AI conversation split into two camps that don’t talk to each other. One is purely technical: architecture diagrams, benchmark tables, model comparisons. Valuable, but silent on the human cost. The other is purely reactive: hype cycles, doom loops, hot takes, tool-of-the-week listicles. Lots of noise. Almost no signal.
What’s missing is the layer underneath both. The layer where you ask: what pattern is actually at play here? The real shape of what’s happening to people, teams, and judgment when machines start recognizing and scaling patterns faster than we can.
That’s what this newsletter is for.
The premise
Every powerful technology is a pattern machine.
Search engines recognize patterns in information. Social platforms recognize patterns in attention. LLMs recognize patterns in language, then generate new outputs based on everything they’ve absorbed.
These tools don’t create meaning. They compress, reflect, and amplify patterns that already exist in us. That makes them incredibly useful. It also makes them risky in a specific way: the easier they are to use, the easier it is to stop thinking about what they’re doing to our thinking. We start treating outputs like answers instead of reflections. We start mistaking confidence for truth, speed for progress, coherence for wisdom.
The builders I respect most already know this. They use these tools with skill and with suspicion. They keep humans in the loop as a real checkpoint on judgment, values, and direction.
Pattern Engine is for those people. And for anyone who wants to become one of them.
What this looks like
Every week, I publish a letter built around a single pattern. Something showing up in both human life and machine systems that deserves more careful attention than it usually gets.
Things like:
Attention. Why what we reward with focus is what grows, whether we’re training a model or training ourselves.
Compression. What happens when nuance gets flattened into a summary, and how that shapes decisions downstream.
Authority. How “the model said so” is quietly replacing “I thought about it,” and what that costs.
Memory. What AI context windows and human storytelling have in common, and where the comparison breaks down.
Trust. The difference between trust that’s earned and trust that’s assumed by default.
Each letter moves through three layers. This is the spine of everything I publish here:
Layer 1: Old Wisdom
What have thoughtful people already said about this pattern? Philosophy, psychology, theology, craft traditions. Hard-won insight that showed up long before the current hype cycle. Simone Weil on attention. William James on habit. The contemplative traditions that trained human cognition for millennia before anyone formalized it in code.
Layer 2: Framework
How does this pattern show up in teams, organizations, and decisions? Where does it give you an edge? Where does it quietly corrode judgment or trust? If you lead people, this is the layer that changes how you run your Monday meeting.
Layer 3: Practice
What does this look like in a real system? Retrieval pipelines, evaluations, agent design, prompt architecture, workflow. Grounded in implementation. If you build things, this is the layer that changes how you build them.
The goal is a letter that’s useful to someone thinking about AI strategy over coffee and to someone debugging a retrieval pipeline at 2pm. If both of those readers feel like the same conversation matters to them, Pattern Engine is doing its job.
Pattern Cards
Every essay comes with a Pattern Card: a condensed, visual reference that distills the three layers into something you can pin to a wall or save to your phone. The card names the pattern, maps how it shows up in people and in machines, and gives you a question to carry into the week.
The cards are designed to accumulate. Week 12 is more useful because weeks 1 through 11 exist. Over time, they become a field guide. Less like a feed, more like a library that gets richer the longer you stay.
Seasons
I build this in seasons. Four per year, thirteen weeks each:
Signal — patterns of attention, meaning, perception, and formation
Systems — patterns of workflow, teams, incentives, and feedback loops
Machines — patterns of AI: context, retrieval, evaluation, automation, and agency
Stewardship — patterns of ethics, power, responsibility, and what it means to govern tools well
The seasons will rotate every year. Same themes, but the examples evolve with the world. Think of it less like a curriculum and more like a rhythm. A way of paying attention on purpose.
Where I’m coming from
I’m a working engineer who builds these systems during the day and thinks about what they mean at night.
My background is in software, infrastructure, and applied intelligence. I care about things working. I also care about what they’re working toward, and whether the people involved are being helped or quietly pushed aside.
I believe in God. That shapes how I think about humility, formation, and what intelligence is actually for. You’ll see it in how I write, but this isn’t a theology newsletter. It’s a place where old wisdom and modern systems meet, and neither one gets to look away.
I believe in craft. In building things well because they should be built well. If you’ve ever felt the pull between “move fast” and “get this right,” you’ll feel at home here.
What comes next
Season 1 is Signal, and the first Pattern Card is about Attention: the mechanism by which raw information becomes structured understanding, the budget you spend every waking hour without ever seeing the ledger, and the reason a two-year-old reaches for his father’s phone.
If you want to be here for it, subscribe.
This isn’t going to be loud. It’s going to be steady, honest, and built to last.
Let’s get to work.
Connor