The Water We Swim In
Three months ago, I came to Egypt. Part of the trip was a long-overdue break. The other part was genuine curiosity — I wanted to understand the tech landscape here, meet the people building things, and share something from the twenty years I've spent in this field, fifteen of them in New Zealand, building platforms, working with teams across different markets and industries.
I met remarkable people. Passionate, driven, building with real intensity. And I wanted to be part of that energy.
But at some point, I stopped.
I was moving through conversations and meetups, scanning what was available, what people were working on, what tools were being used — before I had even decided what I was actually looking for. I was collecting options before I'd asked the question. And somewhere in the middle of that, I recognized the feeling. Not as curiosity. As a pattern.
The same rush. The same quiet pressure of needing to keep up, move fast, catch everything before it passed.
The place had changed. The pattern hadn't.
There's a story David Foster Wallace told in a commencement speech. Two young fish are swimming along and they meet an older fish who nods and says, "Morning, boys. How's the water?" The two young fish swim on for a bit, and eventually one of them looks over at the other and asks, "What the hell is water?"
The point isn't that the fish are stupid. It's that the most obvious and important realities are the hardest to see — because they're everywhere. They're not hidden. They're the thing you're swimming in.
That's what the pattern was. Not a flaw I had missed. Water.
What made Egypt different from New Zealand wasn't the energy or the ambition — both scenes were doing the same thing, chasing the latest tools, tracking what's new, optimizing for speed. The difference was that in New Zealand, that pattern was already fully formed and invisible. It was the water. In Egypt, I could see it still taking shape. And seeing it from the outside, just for a moment, was enough.
The problem was never New Zealand. It was never Egypt. It was a way of thinking we all carry without ever questioning it — the belief that keeping up is the same as moving forward.
The Trap Everyone Is In
The world right now is running at a pace we haven't seen before. Every week brings a new tool, a new framework, a new idea that makes last month's feel outdated. Everyone is moving — not because they know where they're going, but because everyone else is moving.
Distraction has become a culture. Shallow engagement gets sold as speed and productivity. And in tech especially, there's a specific kind of anxiety that comes from feeling like you're always one release behind.
I've spent the last couple of years deep in AI — building AI-powered applications, integrating large language models into enterprise systems, working with these tools every day. That proximity taught me something I didn't expect: working with a technology and truly understanding it are two very different things. You can use a tool daily and still have no real grasp of where it breaks, where it misleads, or where it simply isn't the right answer.
The break gave me space to sit with harder questions. Where is the actual value, and where is the noise? What does this technology genuinely do today, versus what we're told it will do someday? Which fundamentals are shifting, and which ones aren't going anywhere?
What Judgment Actually Looks Like
Here's what I kept coming back to: the developers who will do well in what's coming won't be the ones who chased every new tool. They'll be the ones who understood things deeply enough to adapt — who knew not just how to use these tools, but where to use them, and more importantly, where not to.
That kind of judgment doesn't come from tutorials or keeping up with every announcement. It comes from slowing down enough to actually connect the dots. From being present in the work, not just moving through it.
And that's what the pattern was costing me. Not time. Not productivity. Presence. The ability to actually think, instead of just react.
The One Thing That Compounds
What I found at the end of all this is simple, but not easy.
Every tool gets replaced. Every framework becomes legacy. Every skill that's purely about a specific technology has an expiration date. But the ability to think clearly, to understand deeply, to ask the right question before reaching for an answer — that's the one thing that compounds over time instead of expiring.
AI can write code. It can summarize, suggest, generate, and automate. What it can't do is bring twenty years of judgment about when not to use it, where it misleads, and what actually matters in a given context. That judgment lives in you — in your experience, your hard-won understanding, your genuine curiosity about how things actually work.
That's the one thing AI can't replace. And it's the thing most people are quietly eroding by never slowing down enough to build it.
What Comes Next
So I decided to document this.
Not because I've arrived anywhere final. But because the questions themselves are worth sharing out loud. I'll be writing about everything connected to twenty years of building real things for real users — not from the angle of what's trending, but from the angle of what actually matters and why. Sometimes that means practical breakdowns. Sometimes it means slower reflections like this one.
The first thing I want to break down is something most developers use every day without really understanding — and it's quietly shaping how much you pay, how much you get, and whether the AI you're building with is actually working for you.
If any of this resonates — follow along, push back, share what you're thinking.
Because real understanding doesn't happen alone.