DEV Community

Cover image for What I Would Tell My Younger Self About Learning to Code
Andrew Moody
Andrew Moody

Posted on

3

What I Would Tell My Younger Self About Learning to Code

If I could go back in time and give my younger self some advice about learning to code, I’d have a lot to say. When I first started, things weren’t as easy as they are now—Google didn’t exist, online courses weren’t a thing, and if you wanted to learn, you were stuck with books, magazines, and whatever help you could find from others.

But even with all the resources available today, I see new developers struggling with the same challenges I did: self-doubt, feeling stuck, and wondering if they’ll ever “get it.”

So, if I had a chance to sit down with my younger self, here’s what I’d tell him.

You Don’t Need to Know Everything to Get Started

When I first got into coding, I thought I had to learn everything before I could build something real. But the truth is, you don’t need to master every concept up front. The best way to learn is by doing.

Pick a project. Even a small one. Struggle through it. Google things. Learn just enough to move forward.

Nobody memorizes everything—learning how to find answers is more important than knowing everything off the top of your head.

You’ll Feel Like an Imposter (And That’s Normal)

Even experienced developers feel like they don’t know enough sometimes. The feeling of “I don’t belong” or “everyone else is smarter than me” never fully disappears—but it does get quieter.

The best way to silence imposter syndrome? Keep showing up. Keep learning. The more problems you solve, the more confident you’ll become.

Debugging is a Superpower

When you’re learning, bugs are frustrating. You write code, and it should work… but it doesn’t. And then you stare at it, wondering what went wrong.

What I wish I knew earlier: debugging isn’t just part of coding—it is coding.

Learn to read error messages. Take a break if you’re stuck. Get comfortable troubleshooting—because that’s half the job.

Networking Matters More Than You Think

When I was starting out, I focused only on coding. I thought that as long as I got good enough, opportunities would come to me. But the reality? The best opportunities come from people, not job boards.

Engage in communities (like Dev.to, LinkedIn, or Reddit). Talk to other developers, even if you feel like a beginner. Help others when you can. People remember that.

Your network can open doors that technical skills alone can’t.

It’s a Marathon, Not a Sprint

There were times I felt like I wasn’t learning fast enough. I compared myself to others. I thought I’d never be good enough. But coding isn’t something you master in a few months—it’s a skill you build over a lifetime.

If I could go back, I’d tell myself to be patient. Keep going. The progress you don’t see today will show up later.

Final Thoughts
I’ve been coding for decades, and I still learn new things all the time. If you’re just starting, don’t stress about knowing it all—focus on making small, consistent progress.

What advice would you give your younger self about learning to code? Let’s hear it in the comments!

Heroku

Deploy with ease. Manage efficiently. Scale faster.

Leave the infrastructure headaches to us, while you focus on pushing boundaries, realizing your vision, and making a lasting impression on your users.

Get Started

Top comments (5)

Collapse
 
recklessop profile image
Justin Paul

1000% - Great tips

Collapse
 
andrew_moody_41 profile image
Andrew Moody

Appreciate it! The learning never stops, right?

Collapse
 
eloebo_eniola_1f6c6e741bd profile image
Eloebo Eniola

I feel like these tips hit me in all the right places as a beginner programmer, I appreciate it

Collapse
 
andrew_moody_41 profile image
Andrew Moody

That means a lot—glad it resonated with you!

Collapse
 
bakaaichan profile image
AiChan

Good suggestions, I wish I can know that when I was a beginner.

Playwright CLI Flags Tutorial

5 Playwright CLI Flags That Will Transform Your Testing Workflow

  • 0:56 --last-failed
  • 2:34 --only-changed
  • 4:27 --repeat-each
  • 5:15 --forbid-only
  • 5:51 --ui --headed --workers 1

Learn how these powerful command-line options can save you time, strengthen your test suite, and streamline your Playwright testing experience. Click on any timestamp above to jump directly to that section in the tutorial!

Watch Full Video 📹️

👋 Kindness is contagious

Engage with a wealth of insights in this thoughtful article, valued within the supportive DEV Community. Coders of every background are welcome to join in and add to our collective wisdom.

A sincere "thank you" often brightens someone’s day. Share your gratitude in the comments below!

On DEV, the act of sharing knowledge eases our journey and fortifies our community ties. Found value in this? A quick thank you to the author can make a significant impact.

Okay