I Stopped Trying to Learn Everything

I thought being a good developer meant adding more and more technologies to my stack.

"React? Vue? Angular? Next.js, Astro, Svelte,… ? Gotta Learn ’em all!"

I thought knowing more tools made me a better developer.

Whenever I saw someone building something with a technology I didn’t know, I felt like I was falling behind. So I kept adding more and more things to my list, hoping that if I learned enough, I’d finally feel like I knew what I was doing.

But the list never ended. There was always something else to learn.

The Feeling of Being Behind

I used to open my laptop with the intention of working on one specific project. But somehow, I’d always end up watching a YouTube video about something completely unrelated.

"Maybe I should learn this", I’d think.

And then I’d go down a rabbit hole, watching more videos and reading about more things.

After a while, I’d start thinking, "Damn, there's so much I don't know."

I could spend hours learning about things I didn’t even need for my project. It felt productive because I was learning, but by the end of the day, I’d realize I had spent all that time learning without actually building anything.

I think this is one of the easiest traps to fall into as a developer. There’s always something new to learn. A new tool, framework, language, or technology. And when you see everyone online learning something new, it’s easy to feel like you’re falling behind.

The more you learn, the more you realize how much you don’t know.

Too Many Tutorials

I think tutorials can be a little dangerous, not because they’re bad. They’re actually great and helpful. The problem is that it’s easy to feel like you understand something just because you watched someone else build it.

I’ve done this so many times before. I’d watch a tutorial and think, “Yep, got it.”

Then I’d close the video, try to build it myself, and suddenly I’d be like, “Wait, how did they do that again?”

Skill issue? Yeah, maybe 🫣. But I also think there’s a little more to it than that.

That’s when I started realizing that understanding something and being able to use it are two completely different things.

Building Changed Everything

The biggest improvement for me didn’t come from another course or tutorial. It came from actually building things.

Sometimes I felt like the projects I built were terrible. Sometimes I didn’t even finish them. But every time I built something, I had to make decisions myself. Which library should I use? How should I structure this? Why isn’t this working? Should I rewrite this? Do I even need this feature?

Those questions taught me much more than simply following a tutorial because I actually had to think about the problem instead of just following someone else’s solution.

If I messed something up, I’d usually remember it. And when I finally got something working after struggling with it for hours, that stuck with me too. Those experiences started sticking with me in a way that watching tutorials never really did.

I Still Don’t Know A Lot

I know I’ll never know everything. I still feel stupid sometimes when I realize how much I don’t know, but I’m learning not to let that feeling hold me back.

I don’t want to use “it’s okay not to know everything” as an excuse to stop learning. I still want to keep pushing myself and getting better. I just don’t want to feel like I need to know everything before I can start.

There will always be another framework, another language, another tool, and another developer who knows something I don’t. That’s normal, I guess? I don’t think the goal is to know everything anymore.

The goal is to get better at figuring things out.

If I don’t know something, I can search for it. I can read the documentation, experiment, break things, ask questions, and learn when I actually need to. I don’t need to know everything before I start. I just need to know how to figure things out when I get stuck.

What I’m Trying Now

Instead of asking myself, "What should I learn next?"

I’m trying to ask, "What do I want to build next?"

It’s a small change, but it completely changes how I learn.

If the project needs cloud infrastructure, I’ll learn cloud. If it needs AI integration, I’ll learn it too. The project gives me a reason to learn, and somehow learning feels much easier when there’s a reason behind it.

I’m also trying to accept that I don’t need to understand everything before starting a project. Sometimes the best way to learn something is to start building and figure things out along the way.

It’s Okay To Go Slow

I still get that feeling sometimes, like everyone else is moving faster than me.

Someone gets a new job. Someone launches a startup. Someone learns a new framework in a weekend. Someone builds something that looks incredible.

It’s easy to compare yourself when you’re constantly seeing what everyone else is doing.

But I’m slowly learning that I don’t need to match someone else’s timeline. I just need to keep moving, even if it’s slow.

There are days when I learn a lot, and there are days when I barely make progress. I think that’s okay too. Not every day needs to be productive or impressive.

What I’ve Learned

I don’t want to keep trying to learn every new technology just because I feel like I should know it.

I’d rather get better at taking an idea and actually building it. Sitting down, getting stuck, looking things up, making mistakes, trying again, and eventually turning it into something real. I think that’s a much more useful skill than knowing the basics of a hundred different technologies, and probably a much more realistic definition of being a developer.

So for now, I’m trying to focus less on learning every new technology and more on actually building things. I don’t need to know everything. I just need to keep building, learn what I need as I go, and get better through experience.