Building Before You Feel Ready

By Gaurav Nardia • 21.Feb.2026

Most of the projects I’ve built didn’t start with confidence. They started with curiosity.

Trybit wasn’t built because I knew it would work. It was built because I wanted to see if I could design a real-time challenge system from scratch.

The HTTP Protocol project wasn’t built for production. It was built because I wanted to understand what actually happens under the hood when we type https://.

I’ve learned something important:

You don’t become ready and then build.
You build, and that’s how you become ready.

Shipping > Perfect Planning

For a long time, I believed I needed to:

  • Know system design deeply
  • Master every edge case
  • Write “perfect” architecture

Before shipping anything.

But every meaningful improvement in my skill came from:

  • Breaking my own production code
  • Fixing performance issues at 2AM
  • Debugging real authentication bugs
  • Handling actual users, not test data

There’s no substitute for real friction.

What Shipping Taught Me

1. Systems Thinking

Building full-stack forces you to think in flows:

User → API → Database → Response → UI → State

Once you’ve wired everything end-to-end, abstractions start making sense.

2. Ownership Changes Everything

When you deploy something publicly, responsibility shifts.

You’re no longer coding for fun.
You’re building for someone who might rely on it.

That mindset alone improves quality.

3. Momentum Beats Motivation

Motivation fades.
Momentum compounds.

Small features shipped consistently > One “perfect” release that never happens.

The Real Skill

The real skill isn’t knowing every framework.

It’s being comfortable:

  • Starting messy
  • Iterating fast
  • Improving what exists
  • Shipping anyway

That’s what helped me move from learning tutorials to building SaaS products.

And that’s what I’m continuing to optimize for.

If you’re waiting to feel ready,
you probably already are.

Start building.