I Didn’t Learn to Code. I Started Building Anyway.

For years, the advice was simple. If you wanted to participate in the future, you needed to learn how to code. That meant picking a language, investing the time, and working your way through a process that often felt slow and, at times, frustrating.

I’ve been around technology long enough to understand how important that skill has been. I’ve dabbled over the years and picked up enough to appreciate what developers do. But I never fully crossed the line into being someone who could sit down and build whatever I imagined without running into resistance along the way.

That’s changed.

Not gradually, but all at once.

When Building Became Accessible

Over the past month, I’ve been working with Claude Code. Not in a theoretical way, not watching tutorials or reading about what might be possible, but actually building things and putting them out into the world.

The change has been hard to ignore.

It genuinely feels like something went from black and white to full color. Ideas that used to sit in the background, waiting for the right time or the right skillset, are now turning into real projects much faster than I would have expected.

What surprised me most wasn’t just the speed. It was the removal of hesitation. I’m no longer asking myself whether something is possible. I’m simply exploring how far I want to take it.

What That Looks Like in Practice

In the span of a few weeks, I’ve built out several live projects.

One of them is CruisePlanner.pro, a site designed to be a comprehensive resource for travelers, especially those interested in Virgin Voyages. It’s something I’ve thought about for a while, but the ability to execute on it at scale simply wasn’t there before.

I’ve also been expanding GrowingProfits.com, where I’ve focused on creating practical tools and business calculators that people can actually use in their day-to-day decision making. Instead of just talking about ideas, I’m now able to turn them into something functional.

And then there’s my AI keynote speaker site, which I’ve been able to build out as a true authority resource rather than just a simple landing page. It reflects not only what I do, but how I think about AI and its role in everyday life.

Alongside these, there are smaller projects—games, experiments, and tools—that would have never made it past the idea stage in the past. Now they’re part of the process.

The Real Barrier Wasn’t Coding

Looking back, I don’t think the main obstacle was learning syntax or mastering a programming language.

It was the friction involved in getting from idea to execution.

Every concept used to come with a long runway. You had to learn enough to get started, troubleshoot when things broke, and spend time figuring out pieces that weren’t obvious. That process slowed everything down, and most ideas didn’t make it through.

What’s changed is not that all of that complexity has disappeared, but that it no longer sits in the way of momentum.

Once you can move forward without getting stuck at every step, the entire experience of building starts to feel different.

A Shift in Perspective

There’s been a subtle but important change in how I think about creating things.

Instead of asking whether I’m capable of building something, I’m asking how I want to shape it. That might sound like a small difference, but it changes the entire approach.

You stop thinking like someone trying to become technical and start thinking like someone who builds.

And when that happens, the volume of what you create increases naturally. You’re no longer protecting your time from difficult projects. You’re leaning into them.

The Creative Side of This

What stands out to me is that this doesn’t feel purely technical.

It feels creative.

There’s a sense of experimentation that reminds me of earlier phases of the internet, when publishing suddenly became accessible and people began sharing ideas more freely. Then video followed a similar path, opening up entirely new ways for people to express themselves.

This feels like the next step in that progression.

Building is becoming accessible in the same way writing and video once did. And when that happens, the number of people who participate tends to grow quickly.

What This Means for Everyone Else

This isn’t just relevant for people who consider themselves “technical.”

In fact, it may matter more for those who don’t.

If you have ideas, the barrier to turning them into something tangible is lower than it has ever been. You don’t need to spend years preparing before you begin. You can start, adjust, and improve as you go.

That changes who gets to create.

And it changes how quickly those ideas can evolve.

Where This Leads

I don’t think we’re fully aware yet of what this shift will produce.

What I do know is that I’m building more now, in a short period of time, than I would have thought possible not long ago. Projects that might have taken months are coming together in days. Ideas that would have been set aside are now being explored.

That doesn’t mean everything works perfectly. It doesn’t mean every idea turns into something significant.

But it does mean that the act of building is no longer the bottleneck.

And when that bottleneck disappears, the possibilities expand in ways that are hard to predict.

Most of what I build goes public, too. You can try the growing collection of tools and games at the AI Studio.

If you’ve been sitting on ideas for a while, this might be the moment to revisit them.

You may find that what once felt out of reach is now much closer than it appeared.