What I Wish I Knew Before Starting My Developer Journey 🚀

When I first started learning about development, I thought becoming a good developer meant knowing as many programming concepts, frameworks, and tools as possible.

Over time, I realized it’s not really about knowing everything.

It’s about being willing to learn, experiment, break things, get stuck, and try again.

Here are a few things I wish I had understood earlier:

You don’t need to know everything before building something.
Getting stuck doesn’t mean you’re bad at coding—it means you’re learning.
Documentation is one of your best resources.
Small projects can teach you more than endless tutorials.
Reading and understanding other developers’ code is incredibly valuable.
Consistency beats trying to learn everything at once.
Sharing what you learn can help both you and someone else.

There’s always another framework, language, library, or tool to learn. The goal isn’t to catch up with everything—it’s to keep moving forward.

I’m still learning, experimenting, and figuring things out myself. And that’s probably the best part of being a developer.