7 Years, Too Many Ideas, and a Slight WordPress Addiction.

How I went from building websites to running an automotive community, developing plugins, experimenting with AI, and somehow deciding I needed another project.

It all started with a simple idea. Famous last words.

You know that feeling when you find a piece of software that’s almost perfect?

It does 90% of what you need. The remaining 10%? Apparently, that’s your problem.

Well, that’s pretty much how I ended up here.

I’ve spent the last 7 years building, breaking, fixing, redesigning, and occasionally questioning my life choices over digital projects.

What started with WordPress gradually turned into something much bigger: community platforms, custom plugins, automation, AI integrations, and an ever-growing list of ideas that probably deserve their own project management system.

And honestly? I wouldn’t have it any other way.

WordPress. It’s complicated.

Let’s address the elephant in the room.

Yes, I work with WordPress. A lot.

No, I don’t think installing 47 plugins and hoping for the best qualifies as software architecture.

My journey has taken me through BuddyPress, Youzify, BuddyBoss, and eventually Fluent Community, which has become my personal favorite playground.

Along the way, I’ve tested, tweaked, debugged, and occasionally fought with hundreds upon hundreds of plugins built by other developers. Some were brilliant. Others made me question whether their creators had ever actually tried using them.

But hey, every broken plugin teaches you something. Usually patience.

I’ve spent countless hours figuring out how to make these platforms do things they weren’t necessarily designed to do.

Sometimes that means writing custom functionality. Sometimes it means connecting systems that don’t particularly want to talk to each other.

And sometimes it means staring at a perfectly innocent-looking piece of CSS wondering why the hell it won’t cooperate.

Classic.

Meet DriveZone. The little blog that got completely out of hand.

Back in 2019, I started DriveZone.cz.

Nothing crazy. Just a small, innocent automotive blog where I could publish articles, share interesting stuff about cars, and enjoy working on something of my own.

That was the plan, anyway.

Then came the first new feature. And another one. And another.

At some point, I thought: Wouldn’t it be cool if people could create profiles and interact with each other?

And that’s where things started getting slightly out of control.

That tiny blog gradually evolved into a full-blown automotive community platform with thousands of members, more than 20 features, community spaces, an event calendar, marketplace, automotive tools, and a growing ecosystem of custom functionality.

Somewhere along the way, my innocent little blog turned into a monster project.

A good monster, though. Mostly.

Today, DriveZone is my biggest project, my favorite testing ground, and probably the main reason I occasionally forget what free time looks like.

Whenever I get an idea for a new feature, integration, or unusual way to solve a problem, there’s a good chance DriveZone becomes the first place where I try it.

Some ideas turn into useful features. Others turn into valuable lessons.

Both count as progress.

And because apparently one ambitious project wasn’t enough, I’ve also been working on DriveMap, a location-based application designed to help automotive enthusiasts discover interesting places and connect in the real world.

Because why build something simple when you can make it unnecessarily interesting?

Plot twist: AI entered the chat.

Here’s something I have absolutely no intention of hiding.

I use AI. A lot. But I also know how to code without it.

HTML, CSS, and PHP are part of my everyday toolkit. I’ve spent years working with them, building websites, customizing WordPress, developing functionality, and fixing things that probably shouldn’t have broken in the first place.

I don’t need ChatGPT to change a button color or write a PHP function.

But I also know where my expertise ends.

And that’s exactly where AI becomes interesting.

When a project involves unfamiliar technologies, more advanced architecture, complex integrations, or something beyond my current skill set, I’m not going to spend six months pretending I know everything.

I’ll learn what I need, use the tools available, and figure out how to make it work.

ChatGPT, Claude, coding assistants — whatever helps me turn an idea into something functional.

I’m not going to pretend I sit in a dark room writing every single line of code from memory while drinking my fifth espresso.

Sometimes I write the code myself. Sometimes AI helps. And sometimes we both stare at the same error wondering what went wrong.

My philosophy is simple: use your brain first, AI when it makes sense.

My strengths are understanding problems, designing solutions, connecting systems, spotting opportunities, and figuring out how things should work.

AI helps me move faster and explore technical possibilities that would otherwise take significantly more time.

But there’s a catch.

AI-generated code doesn’t automatically mean good code. You still need to understand what you’re building, test it, debug it, and take responsibility when something breaks.

And trust me, things break.

I see AI as a tool that makes people more capable, not a magic button that makes experience irrelevant.

The important part isn’t who typed the code. It’s whether the damn thing works.

So, what exactly is LetCode.run?

Good question.

After years of developing features, solving problems, and building things primarily for my own projects, I realized something:

Some of those solutions might actually be useful to other people.

That’s why LetCode.run exists.

It’s my personal development space, plugin shop, experimental laboratory, and digital home for ideas that refuse to stay inside my head.

Here’s what you’ll find:

• WordPress plugins — practical tools built to solve actual problems, not just add another settings page to your dashboard.
• Custom development — tailored functionality, integrations, community features, and tools that make existing systems more useful.
• AI-powered solutions — automation, intelligent workflows, and experiments that put artificial intelligence to work.
• Projects and experiments — some polished, some ambitious, and some that probably started with the words „What if…?“

I’m not trying to pretend LetCode.run is some enormous development agency with 200 engineers and an office full of beanbags.

It’s me, my experience, a growing collection of projects, and a slightly unreasonable curiosity about what technology can do.

And I’m perfectly fine with that.

Still learning. Still building. Still breaking stuff.

The more I learn, the more I realize how much there is left to explore.

I don’t claim to know every programming language, framework, or technology. And I definitely don’t believe that being a good developer means memorizing everything.

For me, it’s about knowing how to approach a problem, being willing to learn, and not being afraid to experiment.

I like building things people actually use.

Not just pretty landing pages. Not another generic dashboard. Not features nobody asked for.

Real tools. Real functionality. Real problems solved.

That’s the goal, anyway.

And if something breaks along the way?

Well, that’s what the next version is for.

Welcome to LetCode.run.

Less talking. More building. Let’s make some code run.