There's a version of this story where I tell you I had a roadmap. A clear plan, a vision board, a goal breakdown. I didn't. I had an old PC collecting dust and an idle thought on a Tuesday evening.
That thought was: "Instead of letting this sit here, what if I turned it into something?"
I didn't know what that something was. I just knew doing nothing with it felt wasteful.
One question pulled the thread
I installed Ubuntu Server. Not because I had a project in mind. Because I wanted to see what it felt like to have a home server running. That was it. No deeper reason.
But then something happened that I've noticed happens every time I start anything: my brain asked the next question on its own. "Okay, it's running. What else can I do with this?"
So I set up Jellyfin for media. Then a backup system. Then I started self-hosting small tools I'd been using cloud services for. Each one worked, and each one quietly asked: what's next?
That's when n8n entered the picture. Automation. Workflows. Connecting things together. I built a few small ones — nothing dramatic — but it cracked open a completely different way of thinking about systems.
Curiosity doesn't show you the whole staircase. It just lights up the next step well enough that you want to take it.
The chain reaction I didn't plan
n8n needed a domain to work properly — so I bought one. A practical decision. But having a domain sitting there opened a door I hadn't planned to walk through.
What came next was a personal website. Which led to writing. Which led to documenting experiments publicly. Which led to using AI to build things faster. One practical step quietly unlocked an entire new direction.
Here's the chain, written out plainly:
None of those connections existed in my head at the beginning. Not one of them was planned. Each step was just the most interesting available question at the time.
What actually changed
Here's what surprised me most. The tools were never the real output. The real output was how I started thinking.
Running a home server makes you think about networks differently. Building automations makes you think about systems and triggers differently. Writing publicly makes you think about what you actually believe, because vague ideas fall apart when you try to put them in sentences.
Each project didn't just add a skill. It quietly changed how I approached the next problem. That's the compounding part. It's not visible until you zoom out and look back.
The entire chain — from one idle thought about an old PC to a live website, running automations, and self-hosted infrastructure — took six months. Not years. Six months of following one question at a time.
The thing nobody tells you about curiosity
I think curiosity is a habit that responds to action. The more you follow small questions, the more questions appear. The more you build things — even imperfect, unfinished things — the more interesting the world gets.
Start with what's already in front of you
Looking back, none of this started with a master plan.
It started with curiosity and a willingness to try something with what I already had. That old PC became more than a machine. It became an entry point into building, self-hosting, automation, writing, and creating systems I never imagined I'd touch before.
Most opportunities don't arrive fully visible. They appear one step at a time — usually after you start moving.
You do not need massive resources to begin. You need enough curiosity to take the first step seriously.