Side Projects: The Invisible Competitive Advantage in Tech
How personal experiments sharpen your skills, shape your identity, and open unexpected opportunities
There’s a thought that keeps coming back to me:
In tech, the moment you stop exploring, you slowly start becoming obsolete.
It’s not about age. It’s about mindset.
If you work in software development, product, data, AI, or infrastructure, you already feel the acceleration. New frameworks appear before the previous ones stabilize. AI capabilities evolve monthly. Entire workflows shift within a year.
Keeping up is no longer optional.
But reading about change is not the same as engaging with it. And that’s exactly why side projects matter more than ever.
The OpenClaw Story: When Exploration Becomes Opportunity
I recently came across the story of OpenClaw and its founder Peter Steinberger.
OpenClaw started as a personal exploration. It wasn’t a corporate initiative or a carefully validated startup idea. It was curiosity turned into code. A technical experiment driven by craftsmanship and depth.
That experiment eventually became a strong enough signal that its founder is now going to work at OpenAI.
Not because he “had a side project.”
But because he built something thoughtful, real, and technically meaningful.
Side projects create proof of capability that no résumé can replicate. They show how you think. How you design. How you solve problems when no one hands you a ticket.
That signal is powerful.
From Consumption to Creation
We consume an enormous amount of technical content. Articles, threads, GitHub repos, conference talks. It feels productive.
But there’s a fundamental difference between understanding a concept and building with it.
When you start a side project, you’re forced to make decisions. You can’t stay abstract. You choose the stack. You structure the data. You design the UX. You deal with performance issues. You ship something imperfect.
That process builds depth.
And depth is increasingly rare in a world optimized for speed and surface-level knowledge.
Building ProjectExplore: A Playground That Became a Product
One of the side projects I’ve been building is ProjectExplore.
It started with a simple observation: travel content is everywhere, but discovery is chaotic. On platforms like YouTube, videos are organized chronologically. You scroll through uploads, thumbnails, and titles. Geography is secondary.
But travel is inherently spatial.
So the idea behind ProjectExplore is straightforward: what if you could explore travel content geographically instead of chronologically?
ProjectExplore is a map-based platform where travel creators can pin their YouTube videos directly to real-world locations. Instead of browsing a timeline, you browse a map. You zoom into a region and see what creators filmed there. You can follow a journey visually, understand routes, and discover places in context.
It shifts discovery from “latest upload” to “where in the world.”
From a technical standpoint, it became a rich playground. Working with geospatial data forces different modeling decisions. Performance considerations change when maps and dynamic content are involved. The UX challenges are different because navigation is spatial, not linear.
But the real learning came from the product side.
How do you design something intuitive when the mental model is different from what users are used to? How do you balance simplicity with flexibility? How do you validate whether the problem is real or just interesting to you?
We’re still in an early stage. That’s intentional. Side projects don’t need to emerge fully formed. They evolve through feedback, iteration, and small improvements. Right now, I’m mostly interested in talking to travel creators and travelers, understanding how they discover content, and collecting honest opinions, even (or especially) critical ones.
That’s another thing side projects teach you: humility.
When you build something from scratch and show it to the world, you quickly realize how many assumptions you made. And that’s where the real growth happens.
If you’re curious, you can check it out at projectexplore.app. More than users, I’m interested in conversations.
Side Projects as Identity Work
There’s a subtle shift that happens when you consistently build outside your main job.
You stop seeing yourself only as someone who executes tasks. You start seeing yourself as someone who creates systems, ideas, and products.
That shift changes how you approach your career. It changes the level of ownership you assume. It changes how you think about problems.
Side projects are not just technical exercises. They are identity work.
They define who you’re becoming as a professional.
The Compounding Effect
The biggest misconception about side projects is that their value must be immediate. That they need to generate revenue, go viral, or lead to a job offer within months.
Most don’t.
Their real value compounds quietly.
Each project expands your mental models. Each experiment sharpens your execution. Each iteration improves your judgment. Over time, you connect dots faster. You develop taste. You build confidence.
And occasionally, one project becomes more than an experiment. It becomes a signal. Or a turning point.
Just like in the OpenClaw story.