What building a side project taught me that 10 years at my job never did

I've worked in tech for over a decade. Good salary, interesting problems, smart colleagues. I learned a lot.

But the six months I spent building a side project taught me more about how business actually works than all those years combined.

Here's what employment doesn't teach you—and why every person with a job should build something on the side, even if it never makes a dollar.

Nobody cares about your product

At work, there's always someone whose job it is to care about what you build. A PM prioritized it. A designer mocked it up. Leadership approved it.

When you build your own thing, you face the brutal reality: nobody asked for this. Nobody is waiting for it. The world is indifferent to your existence.

This sounds depressing. It's actually liberating. It forces you to answer the question that employment lets you avoid: why should anyone care?

I spent three weeks building a feature I was convinced users needed. Launched it. Crickets. That silence taught me more about product-market fit than any strategy meeting ever did.

Pricing is emotional surgery

At my job, I never thought about pricing. Someone else handled that. The product cost what it cost.

Setting my own price felt like standing naked in public. Every part of my brain screamed "make it cheaper" or "make it free" or "nobody will pay for this."

Charging money forces you to confront your own beliefs about value. Do I deserve to be paid for this? Is my work worth anything? These questions never come up when you're collecting a salary.

The first time someone paid me $29 for something I built in my bedroom, I felt something I'd never felt at work: I earned this. Not because someone approved my performance review, but because a stranger decided my creation was worth their money.

Marketing is just talking to people

I used to think marketing was a dark art practiced by people with business degrees and big budgets.

Turns out, marketing is mostly just telling people your thing exists and explaining why it might help them. That's it.

I spent years avoiding "marketing" because it felt gross. Then I started doing customer interviews and realized: this is just having conversations. Asking questions. Listening. Sharing what I learned.

The mystique around marketing exists because most of us have never done it. Employment keeps you in your lane. Building something forces you into every lane.

Support is where you actually learn

At work, customer feedback is filtered through multiple layers before it reaches you. Tickets get triaged. Issues get prioritized. By the time something lands on your desk, it's been sanitized.

Running my own support inbox was a revelation. Real people, with real frustrations, explaining exactly what's wrong with my product. No buffer. No filter.

Some messages stung. Some were unfair. But buried in those complaints was a map of exactly what I needed to fix. I just had to be willing to read it.

You have more time than you think

The biggest lie I told myself for years: I don't have time for a side project.

I had plenty of time. I was just spending it on things that felt productive but weren't: endless Twitter scrolling, "research" that was really procrastination, optimizing systems that didn't need optimizing.

Building something with constraints—nights, weekends, stolen lunch breaks—taught me what my time was actually worth. When you only have two hours, you don't waste twenty minutes setting up the perfect development environment.

Constraints create clarity. My best work happened not despite the time pressure, but because of it.

Failure hits different when it's yours

I've failed at work. Missed deadlines. Shipped bugs. Got critical feedback.

But there was always a buffer. The company absorbed my failures. My salary didn't change. Life went on.

When my side project failed to convert a single user from a launch, the failure was mine alone. Nobody to blame. Nobody to share it with. Just me and my choices.

This sounds painful. It was. But it was also the first time I truly felt ownership of something. The failures were mine—but so were the wins.

The point isn't to quit your job

I still have my day job. I'm not trying to build the next unicorn or achieve "founder freedom" or whatever the current aspiration is.

But building something on the side changed how I show up at work. I ask better questions. I think about the customer differently. I understand parts of the business I used to ignore.

The point isn't to escape employment. It's to escape the limitations that employment puts on your understanding of how value is created, captured, and delivered.

You don't need a revolutionary idea. You don't need to go full-time. You don't need to make money.

You just need to build something that's yours—and learn what that teaches you.