Pragmatic advice to start learning to code

February 2023 · Derick Zr · 4 minutes read

"How do I start learning to code?"

I get this question more than any other.

Usually from people who think they're too late, or not smart enough, or need the perfect course before they can write their first line.

I started in 2019. No CS degree. No bootcamp. Just me, a laptop, and a lot of bad code.

Here's what I learned about learning to code.

You Need to Actually Like This

When I started, I fell in love with programming. Not because it was easy. Because it was interesting.

If you're only learning to code for the money, you'll quit. I've seen it happen.

The learning curve is steep. You'll spend hours debugging a typo. You'll rebuild the same thing five times because you didn't understand state management.

If you don't find that process at least somewhat interesting, you won't make it. Programming is not a destination. It's a really long journey. You won't learn everything in six months. You won't even learn everything in five years.

Don't Try to Learn Everything

I see this constantly: beginners trying to learn React, Vue, Angular, Node, Python, databases, Docker, Kubernetes, and blockchain all at once.

They burn out in three weeks.

Don't do this.

Pick one language. Learn the basics. Variables, loops, conditionals, functions. That's it for now.

Think of it like learning to drive. You learn to start the car, move forward, stop, and park. You don't start with drifting.

Same with code. Master the basics first.

Start With the Basics

Foundation matters. You can't skip to React if you don't understand how variables work.

I started with two resources:

Pick one. Just start.

Learn variables, if-else statements, loops, and basic data structures. That's your foundation.

cartoon
cartoon by hackles

Practice Until It Hurts

Reading about code won't make you a developer. Writing code will.

Impostor syndrome is real. The only way to fight it is by building things and proving to yourself that you can.

Here are the platforms I used:

  • HackerRank - Good for building language fundamentals
  • Codeforces - Problem sets with editorial explanations
  • LeetCode - Best for interview prep

Pick one. Start solving problems.

Build Real Projects

My first project was my own website. Basic, static, nothing fancy.

Then I built a site for a friend's startup. Still static.

Then I wanted to try full-stack. So I built a developer community app. Users could create posts, delete them, follow each other, search. Full CRUD.

It was messy. The code was terrible. But I learned more from that one project than from months of tutorials.

My friend Galien wanted to learn Web3. He got stuck trying to figure out the "right" way to do things.

Turns out there isn't one. He just picked a path and started building.

Now he's a Web3 developer with multiple projects shipped.

The lesson: stop looking for the perfect way. Just start.

Here are some project ideas:

  • Gamer? Build Tic-Tac-Toe, Sudoku, or Flappy Bird
  • Data nerd? Try web scraping or stock chart analysis
  • Want to learn frontend? Build your portfolio
  • Want full-stack? Build a blog or bookstore

Pick one. Build it. Get stuck. Debug it. Learn.

That's how you actually become a developer.

Get Feedback

You can't see your own mistakes. You need other people to point them out.

Ways to get feedback:

  • Share your code in online communities (Reddit, Discord, GitHub)
  • Pair program with someone more experienced
  • Join code review sessions
  • Find a mentor

Don't code in isolation. You'll develop bad habits that are hard to break.

The Truth About Learning to Code

It's not about talent. It's not about the perfect course. It's not about having a CS degree.

It's about consistency. Showing up every day. Writing bad code and making it better.

Start small. Build things. Get feedback. Repeat.

That's it.

Pragmatic advice to start learning to code