Operational

Thinker ∴ Researcher ∴ Hacker ∴ Coder ∴ Founder ∴
Based in Bucharest.

Back to Blog

Things I Learned / Mistakes I Made

13+ years of building things. Some worked. Most didn't. Here's what stuck.

November 19, 20255 min

I've wasted a lot of time. Chased the wrong things. Built products nobody wanted. Joined projects that went nowhere.

I don't see these as regrets. They're just expensive lessons.

Mistake: Chasing Perfection

Early in my career, I thought good code meant perfect code. Clean architecture, comprehensive tests, zero tech debt. I'd spend weeks refactoring systems that worked fine.

What I learned: Perfect is the enemy of shipped. Good enough is usually good enough. Tech debt is only debt if you're still around to pay it.

Mistake: Not Saying No

I used to say yes to everything. Every project, every feature request, every "quick favor." I thought being helpful meant being available. It didn't. It meant being scattered.

What I learned: Your time is your most valuable asset. Guard it. Say no to things that don't align with where you're trying to go. Opportunity cost is real.

Mistake: Building Without Validating

I've built entire products based on assumptions. Spent months coding before talking to a single user. Convinced myself that "if I build it, they will come."

They didn't.

What I learned: Talk to users early. Ship MVPs. Get feedback before you're emotionally invested in the solution. Most ideas are wrong-find out fast.

Mistake: Ignoring the Business Side

For years, I thought being a great engineer was enough. I focused on code quality, performance, architecture. I ignored distribution, marketing, business models.

What I learned: Code is just a tool. What matters is solving real problems for real people in a way that's sustainable. The best code in the world is worthless if nobody uses it.

Mistake: Underestimating Soft Skills

I used to think technical skills were all that mattered. I was wrong. Communication, empathy, negotiation-these determine how far you go.

What I learned: Your ability to work with people, explain complex ideas simply, and build trust is just as important as your ability to write code.

What Actually Matters

After 13+ years, here's what I wish I knew earlier:

  • Ship constantly: Momentum beats perfection.
  • Talk to users: Build what people need, not what you think they need.
  • Invest in relationships: Networks compound over time.
  • Learn in public: Share your process, your failures, your wins.
  • Stay curious: The moment you think you know everything is the moment you stop growing.

The mistakes were necessary. The detours taught me things the straight path never would have.

You can't avoid failure. You can only fail faster, learn quicker, and keep moving forward.