← Back to blog
June 1, 2026 · 5 min read

10 Years of Building Things. Here's What Actually Stuck.

I've built software, a gym, an academy, and now an AI company. The lessons that actually transferred across all of them are simpler than I expected.

Quick summary

Ten years of building across tech, a gym, a fitness academy, and now an AI company. Some patterns show up no matter what you're building. These are the ones that actually changed how I work.

I've been building things since I was 17.

Not all of it was tech. I built a gym. I built a fitness academy. I've built software products. Now I'm building an AI company called CyberCore.

Different industries. Different customers. Different problems. But some things show up everywhere. These are the ones that actually changed how I work.

The first version is supposed to be embarrassing

I used to wait until something was good enough before showing anyone. That meant I'd spend months on something, release it, and only then find out I'd been solving the wrong problem.

The gym version of this: I spent weeks designing a workout program before asking a single potential client what they actually wanted. Turns out they weren't thinking about program design. They were thinking about showing up consistently.

Now I show things early. Not because I've given up on quality, but because quality requires knowing what you're optimizing for. You don't find out what matters until you put something in front of a real person.

Systems beat motivation every single time

When I was running the gym, I'd see this pattern constantly. Someone starts strong, motivated, energized. Six weeks in, motivation drops (it always does), and the habit collapses.

The people who stuck around long-term weren't the most motivated. They were the ones who made it hard to skip. They scheduled workouts at the same time. They found a training partner. They paid for coaching.

Same thing with building products. If your process depends on being in the mood, you're going to have bad weeks. I don't decide whether to write code every morning. I just have a block of time where that's what happens.

You learn more from the thing that failed

My gym almost closed twice. Once from a cash flow problem I didn't see coming. Once from a competitor opening 500 meters away.

Both times I learned more in 3 months than in the previous year of things going fine. The cash flow crisis taught me to always know my runway. The competitor crisis taught me that you don't compete on price if you want to stay alive.

The hard part is that you have to be willing to look clearly at what went wrong. The temptation is to explain it away. Sometimes external factors are real. But usually there's also something you did or didn't do, and that's the part worth sitting with.

Nobody cares as much about your product as you do

This sounds obvious. It took me years to actually internalize it.

When I was building software, I was convinced that if people just understood how good it was, they'd use it. I spent a lot of energy on features and almost no energy on telling people about them.

People are busy. They have their own problems. You have to earn their attention, repeatedly, over time. The product is only half the job. The other half is helping people find it and understand why it matters to them specifically.

Slow decisions are often expensive ones

I had a business situation once where things were clearly not working. I knew it wasn't working for a long time before I did anything about it. I kept thinking it would get better.

It didn't get better. And the months I spent hoping cost a lot more than the uncomfortable conversation would have.

I try to make the hard calls faster now. Not reckless. But when I'm avoiding a decision, I'm usually also avoiding the information the decision would give me.

The overnight success was a decade in the making

I see people building things who are frustrated that they're not getting traction after three months. I get it. I was there.

But I've also seen what it actually takes. The people who look like they came out of nowhere usually didn't. They were building skills, audience, relationships, or credibility for years before the thing that looked like a big break.

I started coding when I was 17. I spent years building in different directions before AI became the focus. Everything that looked like a wrong turn contributed something: fitness taught me about behavior change. Business operations taught me about cash and priorities.

There's no wasted time if you're paying attention.

The thing I'd tell my 17-year-old self

Just build something. Anything. It doesn't have to be good. It doesn't have to work. The act of finishing one thing teaches you more than reading about ten things.

The rest you figure out by doing it again.