I Was Waiting to Be "Ready." Building Projects Changed Everything.

Vaidehi Yadav — Wed, 05 Aug 2026 12:29:27 +0000

When I first started learning to code, I believed I needed to complete every course, watch every tutorial, and understand every concept before I could build something meaningful.

I was wrong.

The more I learned, the more overwhelmed I became. Every roadmap introduced another framework, another library, another "must-know" technology. It felt like the finish line kept moving further away.

So one day, I decided to do something different.

Instead of learning everything first, I started building.

That single decision changed the way I learn.

Working on real projects taught me lessons that no tutorial ever could. I learned that a tiny mistake—a single missing character, an extra space, or a typo—can stop an entire application from working. Hours of debugging can come down to one small error.

And when the application finally runs without a single error?

That feeling is hard to describe. It's relief, excitement, and motivation all at once. Those moments remind me why I love programming.

Since I can't afford expensive courses, I use AI tools as mentors. They don't replace my thinking—they help improve it. When I'm stuck, they explain concepts, point me in the right direction, review my code, and challenge my ideas. They help me learn faster, but I still have to understand and build everything myself.

Over time, I discovered something else about myself.

I genuinely enjoy solving problems.

Whenever I think of a project, I don't immediately start coding. I spend time understanding the problem first.

Why does this problem exist?
Is there a simpler way to solve it?
Can the user experience be better?
What would make this idea different from what's already available?

Once I have a direction, I create a prototype, experiment with different approaches, refine the idea, and keep improving it. Seeing an idea slowly turn into a working product is one of the most satisfying parts of my journey.

I'm still a student.

I still make mistakes almost every day.

I still Google things.

I still get stuck.

But I've stopped seeing those moments as signs that I'm not good enough.

They're simply part of building.

Looking back, I think the biggest lesson I've learned isn't a programming language or a framework.

It's that you don't become a better developer by consuming more tutorials.

You become better by building, making mistakes, fixing them, and repeating the process.

I'm still at the beginning of my journey, but if there's one piece of advice I'd give to anyone who's waiting to be "ready," it's this:

Start building before you feel ready.

You'll learn more from one real project than from dozens of tutorials you never apply.

This is only the beginning of my journey, and I'm excited to see where building takes me next.

What has been the biggest lesson you've learned while building your own projects? I'd love to hear your story.

My first ever idea

Vaidehi Yadav — Mon, 27 Jul 2026 13:52:47 +0000

Why I'm Documenting My Computer Science Journey

I'm a Computer Science student at the beginning of my software engineering journey.

Like many students, I often felt overwhelmed by the number of things I "should" learn—DSA, backend development, AI, Git, cloud, open source, hackathons... the list never seems to end.

Instead of trying to appear like I know everything, I've decided to do something different.

I'll document what I'm building, what I'm learning, the mistakes I make, and the lessons I pick up along the way.

One of the ideas I've been exploring is ImpactIndia—a platform aimed at making volunteering and community engagement more accessible for young people. Whether it becomes a successful product or simply a valuable learning experience, I want to share the engineering decisions, challenges, and insights that come from building it.

This blog isn't about pretending to be an expert.

It's about becoming one—one project, one bug, and one lesson at a time.

If you're also learning, building, or figuring things out as you go, I hope you'll find something useful here.

Here's to the journey.

DEV Community: Vaidehi Yadav

I Was Waiting to Be "Ready." Building Projects Changed Everything.

My first ever idea

Why I'm Documenting My Computer Science Journey