The Hobby Isolation Paradox
There's a specific kind of exhaustion that comes with being the tech person in your family.
It's not the fixing. You can fix things. It's the explaining. Bridging the gap between what's actually happening and what will land for the person standing over your shoulder. You get good at simplifying. Fast at it. But after a while the simplifying starts to feel like a tax. And eventually, without really noticing, you stop bringing certain things up at all. Not because people don't care about you. But because you already know how it ends.
Hobbies are supposed to fix this.
Common ground. A talking point. Something to bond over. The implicit promise of a hobby is that it connects you to people — other enthusiasts, curious friends, family members who ask how it's going. For most hobbies that promise holds. You pick up candle making and suddenly you have something easy to talk about at dinner. Everyone knows what a candle is. The vocabulary is shared, the concept of enjoying it makes intuitive sense.
But some hobbies break that promise entirely.
Right now the thing I'm most excited about is agentic engineering — building software by collaborating with AI. Not using it as a shortcut. Using it as a creative partner. It's what I think about when I'm not working. What I open my laptop for on a Saturday morning before I've had coffee.
And almost nobody in my day-to-day life gets it.
I've tried explaining it. Someone asks what I've been up to, and I start with "building software with AI" and I can see it happen — the polite nod, the slight glaze. Not because they don't care. They're trying. But the words don't land. "AI agent" means nothing to most people. "Prompt engineering" sounds like corporate jargon. Before I can get to the interesting part I'm already three layers deep in background, and the conversation has moved on.
Even when I find the right simplification, there's another wall waiting. Because building software on a Saturday morning doesn't register as a hobby. It sounds like work. The idea that it could be play — that it's the thing I look forward to all week — that part doesn't compute.
So I stop bringing it up. Or I start to, feel what's coming, and just let it go.
The thing that was supposed to give me community becomes the thing I can't even mention.
Recently someone I work with mentioned Claude Code in passing. Just dropped it into conversation like it was nothing. The same energy, the same excitement, that I'd been wanting to express. We were already two steps into a conversation I didn't have to set up.
That's part of why I write here. Not to explain things to people who don't get it — but to find the ones who already do. The builder who's also lying awake thinking about what's coming. The person who gets why this stuff is fun, not just useful.
On the flip side: being island-like with your content means it stops compounding. The silence isn't just from nobody reading — it can also be because the work itself isn't wired to pull people deeper.