5 Time Wasting Habits of Programmers

Habits can destroy or build our careers. So choose them wisely.

Abrar Masum
Level Up Coding
Published in
3 min readOct 20, 2021

--

Photo by christopher lemercier on Unsplash

Time is the most valuable asset we all know. Every great developer I know values their time so much. I think it’s one of the main reasons behind their success.

Wasting time is a sin in my eyes. You can not give me one simple example that can justify wasting your precious time.

I have seen some developers who waste their time but didn’t know that. Because while doing these things, they thought they were working. But they didn’t know they were wasting time.

Let’s discuss those.

Unnecessary Ego

Everyone gets stuck in some situations or problems. The best strategy is to try by yourself for 5–10 minutes to figure that out. Whether you figure it out by yourself or not, your next task should be to search for it on the internet.

Don’t waste your time and your employer’s money by some unnecessary and silly ego that you have to solve the problem by yourself without taking outside help. Even you figure the solution by yourself, search for 10–15 minutes to look for a better solution.

No one can solve all the problems. If you can’t solve all problems, it won’t make you any less programmer. Even some of the best programmers might get stuck in some simple problems on a bad day.

Not using built-in functions

Built-in functions are developed for a reason, right? It’s developed to save developer’s time. 99 out of 100 times, a built-in function will perform better than your developed function.

So, don’t waste time. If you love to develop things on your own, develop a side project or something else. And search on the internet if you think there might be a built-in function for your solution.

Perfectionism

You don’t need to invest 20 hours of your time on how the button would look when it’s pressed.

I won’t blame you if you are a perfectionist. Sometimes it’s a good habit. But sometimes, it kills time for you and others. Once in my team, a developer wasted a full day wasting his time on how to cut the number of…

--

--