Member-only story
5 Bad Developer Habits You Need To Ditch Right Now
Not all bad habits are tech-related, some of them are really hard to spot

We all have our bad habits.
Some of them are minor (like programming in JAVA for instance) and some others are really bad, working against us, and preventing us from learning and improving our work.
And while we, developers, are very technical people, these aren’t “technical bad habits” per se, but rather, they’re very common amongst the tech folk. And the fact that they’re not specifically related to technical problems makes it even harder to identify and get rid of. Heck, some of them are so rooted in our industry that some developers might see them as the proper way of working.
This is why I wanted to cover the top five bad habits that developers need to get rid of right away. So let’s get to it!
Thinking “Tutorial Hell” Is Actually “Tutorial Heaven”
You’ll never have everything you think you need to start building something before you, indeed, start it. So stop trying to learn it all before you build your first solo project.
There are two phases to learning how to code:
- You read about it for a while to get the gist of how things work and some of the key processes (like compiling, linting, testing, etc).
- You hit your head against a wall repeatedly until you break it, then you find the next wall and start over again. In other words, the good ol’ “learn by doing.”
It’s scary, I know, especially for the first one, you have no prior experience which can cause you to feel lost, without knowing where to start. But it’s also normal; the key here is to start small. Don’t try to build an Instagram clone as your first project. Park that one for the future, and start with something easier, with fewer features.
And for the love of everything that is holy, do not try to build your “original super cool and brand new no one has ever done something like this before” idea for your first project. You’ll be lost without knowing where to start. This is because you lack prior experience in programming, and you’ll be extra lost without knowing what…