Coding Habits #56

 

Habit – 1

Not Using Google

I can’t believe how many people use stack overflow or any social media groups as first place to ask their question. If you don’t use google as your first place to look for help, forget about getting a good programmer.

 

Habit – 2

CTRL + C, CTRL + V

The general rule should always be: don’t copy code, you haven’t written on your own. Neither from stack overflow or from GitHub. I always write off new code. That way I remember and understand it much better.

 

Habit – 3

Having Your Phone Next to You

We all know how tempting it is to take a look at your phone when your LED blinks. If you disrupt your coding focus like that, you will never get into the flow state you really need to be in as a programmer.

 

Habit – 4

Trying to Write Perfect Code

Striving for perfection will give you everything but perfection. Don’t spend 80% of your time trying to make 20% of it perfect.

 

Habit – 5

Not Planning Ahead

If you just jump coding a project without a plan, you will fail. If you never plan your projects and you wonder, why you always lose motivation after some time. This is the reason fucked up your code. So it’s no fun for yours to work on it any more.

 

Habit – 6

Trying to Looks Smart

Don’t try to make your code look super smart if readability suffers. You don’t need a crazy one-liner solution. You need code you can easily understand 2 weeks later.

 

Habit – 7

Learning Without Structure

If you start a new projects and don’t know what exactly you want to learn with that, you’re doing it wrong. I recommended to learn one or two new concepts in every projects you start.

 

Habit – 8

Blaming Other

So many programmers I met are super arrogant if it comes to which code is the best and they blame others for ad code. Don’t be like these people be humble, listing to feedback and don’t assume you are always right.