Your Years of Experience Are Yours to Build

One question I've been asked a few times is:

"How did you get experience building all these different kinds of products?"

The honest answer is...

I stopped waiting for experience to come to me.

Don't get me wrong. Working in a company teaches you things you simply can't learn anywhere else. I've been fortunate to work with incredible teams, including in fintech where I got to see what it means to build software that processes serious volume. Those experiences shaped how I think about engineering, reliability, collaboration, and shipping at scale.

But when I look back at the biggest leaps in my career, most of them didn't happen because I changed jobs.

They happened because I built something.

Something people could actually use.

Something that could fail.

Something that forced me to figure things out.

Over the last few years, I've launched marketplace products, booking platforms, ecommerce solutions, internal tools, and products for clients across different industries. Every single one stretched me in ways I wasn't expecting.

And looking back now, I think one of the greatest advantages a developer can give themselves is realizing this:

Your years of experience aren't just accumulated. They're built.

One thing I've noticed is that every company naturally gives you a piece of a much larger system.

You might own the frontend.

Maybe you're responsible for backend services.

Maybe infrastructure.

Maybe product.

Whatever your role is, you're contributing to something bigger.

There's nothing wrong with that.

In fact, that's exactly how great teams work.

But when you decide to build and launch your own product, suddenly every piece belongs to you.

You're making product decisions.

Choosing technologies.

Designing databases.

Setting up infrastructure.

Writing copy.

Integrating payments.

Handling customer support.

Talking to users.

Fixing bugs that only appear after someone pays real money.

It's exhausting.

But it's also one of the fastest learning environments you'll ever create for yourself.

I've built projects that never saw the light of day.

They taught me programming.

The products I launched taught me business.

There's a huge difference.

Once real people start using something you've built, everything becomes different.

Users don't behave the way you imagined.

Features you thought were obvious suddenly confuse people.

Tiny bugs become expensive.

Support messages start arriving.

People ask for features you never considered.

You begin making decisions with consequences instead of assumptions.

That's where real experience starts.

Flextable taught me about marketplace dynamics, supplier acquisition, and trust.

Penless taught me how difficult matching people actually is.

Building ecommerce platforms taught me how differently customers think compared to developers.

Working with clients taught me that building software is only half the job.

Communication matters just as much.

Looking back, I don't think any of these products became valuable because they were perfect.

They became valuable because they forced me to grow.

Every launch exposed another gap in my thinking.

Every mistake became a lesson I carried into the next product.

One thing I appreciate now is that experience compounds.

The first marketplace taught me what marketplaces are.

The second taught me what I missed the first time.

The third started revealing patterns.

By the fourth, some of those decisions became instinct.

The same thing happens in every domain.

You stop relying on tutorials.

You start relying on judgment.

And judgment is one of the hardest things to teach.

Build something real.

Not because it needs to become a billion-dollar company.

Not because every side project has to succeed.

Build it because nothing accelerates growth like putting your work in front of real people.

Choose a problem you genuinely understand.

Keep the first version small.

Launch earlier than you're comfortable with.

Listen carefully.

Improve it.

Then repeat the process.

You'll be surprised how quickly your confidence and your experience begin to compound.

Some products will succeed.

Some won't.

I've experienced both.

But even the products that didn't become businesses still gave me something incredibly valuable.

The lessons stayed.

The mistakes stayed.

The technical decisions stayed.

The conversations with users stayed.

Nobody can take those away.

That's why I believe your career shouldn't only be measured by the number of years you've worked.

It should also be measured by the problems you've solved, the products you've shipped, and the lessons you've earned along the way.

Because in the end, your years of experience are being written every day.

The question is whether you're waiting for someone else to write them...

or whether you're building them yourself.