In this blog I will teach you how taking break can improve your productivity. I am writing this blog post from the perspective of a software developer. But even if you are not a developer, reading this blog post might help you.
I am a full stack web developer. It is almost 3 years, I have been coding. I code everyday. Sometimes not so much but most of the time a lot. Some days may be 8-9 hours.
Absolutely not. Most of the time I do this:
And end of the day:
Because this is the reality. We do less coding more debugging.
so Maybe you have started your day fully motivated. You have set a goal for your day. So you started coding. After sometime you got stuck in some part of the code. You have been debugging your code for hours. You have done hundred of print statements, tested so many variations. But none them didn't work.
But when you open the same code in the next day, quickly you started to feel like you are stupid. Why? Because you have made a stupid mistake. Maybe you have just missed a number or did a if check instead of if not check or so on. You have wasted the whole day for a stupid bug which you could have solved in a minute.
Don't worry if you feel stupid. This happens to all of us. From a begginer to a experienced FANG(Facebook Apple Netflix Google) engineer.
Short and long answer is yes. The solution is in front of you. The solution is taking break. Yes, taking break is the most efficient solution to me. How?
Your brain produce less solutions and ideas to solve any problem. Your eyes get sleepy. And all of your code simply start to look the same. You apply a lot of approach to find and solve the problem but you don't succeed. Because your eyes didn't search efficiently and that evil bug remains hidden.
But in the next day when you will see the code again you will easily find the bug. How? Because you just took a break to heal your body. And your brain can do its work efficiently. You can now easily now find that stupid bug in your code. And you don't have to waste your time.
I use a 15 minute rule. I start coding normally. When something went wrong, I look at clock and note the time. My goal is to solve that bug in 15 minutes. If I succeed then I am happy.
If I don't succeed then I stopped coding that part of the code. I usually either work on other code or do any other thing. But I won't think about that bug anymore. After taking some break, I get back to that bug. And It gets so much easy to solve.
Now it doesn't always work on first try. Sometimes it might need multiple try.
But it works. I personally set 15 minute. And also it doesn't need to be 15 minute break. It is up to you.
I think you should try this method. There is no harm in trying this method.
So that's it for today. If you like this blog then give it a 💖 reaction. If you have any question, then you can connect to me on any social media as @thatanjan
Until then, stay safe and be happy 🙂
My name is Anjan. I am a full stack web developer from Dhaka, Bangladesh.
I can create complex full stack web applications like social media application, blogging, e-commerce website and many more.
I love to solve problems and develop new ideas. I also enjoy sharing my knowledge to other people who are wiling to learn. That's why I write blog posts and run a youtube channel called Cules Coding
Instagram (personal): @thatanjan
Instagram (youtube channel): @thatanjan
Why would you subscribe to Cules Coding?
Cules Coding will teach you full stack development. I will teach you not only the basic concepts but also the advanced concepts that other youtube channels don't cover. I will also teach you Data Structures and Algorithms with abstraction and without Math. You will also find many tutorials about developer tools and technologies. I also explain advanced concepts and technologies with simplicity.
Subscribe to Cules Coding
so that my friend you don't miss any of these cool stuffs.