DEV Community

Cover image for 1 Bad Habit I Used To Have When I First Started Learning Web Dev—And How I Broke It
Soulis
Soulis

Posted on

4

1 Bad Habit I Used To Have When I First Started Learning Web Dev—And How I Broke It

Most devs got straight to tutorial hell and never come back.

When I started learning Web Development, I did like many aspiring developers do. I follow a tutorial to learn a tool, then another, then another and another without any purpose, mission or achievable goal. I learned a lot of things for the sake of learning-which isn’t a bad thing if the goal is to explore and try things unless you blindly follow tutorials and don’t practice anything.

Theorical knowledge will never lead you to anything good.

I used to jump between tutorials and resources without actually building anything-I had been doing this for years.

Rock bottom for me was when I realized that, despite consuming countless hours of content, I couldn’t build even a basic project from scratch. I was frustrated, overwhelmed, and lacking confidence-It was terrible.

How did I break this bad habit?

I decided to adopt a "learn by doing" approach and focus on small, manageable projects where I could immediately apply what I was learning.

Everything changed as soon as I committed to building something for every concept I learned.

And honestly, I saw almost immediate results.

  1. I became more confident in my coding skills.
  2. I built a portfolio of small projects that showcased my progress.
  3. I started understanding how different pieces of web development fit together.
  4. I gained the momentum to keep learning and improving.

So, if you find yourself jumping between tutorials without actually building anything, I encourage you to learn from my mistakes.

And start building small projects with every new concept you learn.

You might also like:

If you enjoyed this and want more, follow me on twitter for updates! You can also subscribe to my newsletter for exclusive content. Your support keeps the creativity flowing! 😊

Heroku

Build apps, not infrastructure.

Dealing with servers, hardware, and infrastructure can take up your valuable time. Discover the benefits of Heroku, the PaaS of choice for developers since 2007.

Visit Site

Top comments (4)

Collapse
 
ezek-iel profile image
𝙴𝚣𝚎𝚔𝚒𝚎𝚕

I also personally suggest reading books because the code are already written and the reader will need to understand the code hence increasing the reader's ability to read and understand the purpose of code.

it's just that books can get outdated easily

Collapse
 
soulis98 profile image
Soulis

100%

Collapse
 
adamu_abubakar_3591cf5968 profile image
Adamu Abubakar

Timely. Currently working on breaking that habit. This constant imposter syndrome keeps getting the better of me. Will work religiously on it following what you've advised.

Collapse
 
soulis98 profile image
Soulis

Remember brother.

The greatest skill you can unluck is the ability to reinvent yourself, adapt and overcome anything.

Start by your beliefs because they'll help you or poison your mind.

A Workflow Copilot. Tailored to You.

Pieces.app image

Our desktop app, with its intelligent copilot, streamlines coding by generating snippets, extracting code from screenshots, and accelerating problem-solving.

Read the docs

👋 Kindness is contagious

Please leave a ❤️ or a friendly comment on this post if you found it helpful!

Okay