Twenty-five years.
Six startups.
Two exits.
Four spectacular crashes into concrete walls.

People often ask me which taught me more—the wins or the losses.

The honest answer: you don’t get one without the other.

The exits validated instincts. They confirmed that when product, market, timing, and people line up, things move fast—almost effortlessly. You feel momentum. Customers pull you forward. Teams operate with clarity and purpose. You start to recognize patterns that work.

That’s valuable.

But the crashes?
Those were expensive. Brutal. Humbling.

They forced me to question assumptions I didn’t even know I was making. They taught me how fragile conviction can be when it isn’t backed by reality. They sharpened my ability to spot early warning signs, ask uncomfortable questions sooner, and trust that quiet internal signal when something feels off—even if the data hasn’t caught up yet.

That’s earned wisdom.

Along the way, I also had the privilege of working at Google, Meta, and Netflix—seeing execution at a completely different scale. World-class systems. Relentless focus. Talent density. A reminder that “moving fast” means very different things when reliability, trust, and millions of users are on the line.

I’ve seen both extremes:
Scrappy startups and tech giants.
Failure and massive success.
Chaos and precision.

That contrast reshaped how I think about building.
And it’s directly influencing what I’m working on next—what I believe may be my most important venture yet.

If you’re building something—or thinking about it—what’s the hardest lesson you’ve learned so far?

Not (only) the trophy story.
The scar.

How can you debrief it and improve?