5 answers
Asked
408 views
[Computer Programming/Game Development/Web Development] How often do you multi-task while working?
What I mean by when I say this is, whenever you're programming or coding rather, how often will you take a break to relax yourself by reading or watching something.
Login to comment
5 answers
Updated
Chandler’s Answer
I don't take breaks rather just watch shows or movies while I am doing it. If it is work from home however, Ill play World of Warcraft where there is 30-45 minute queues and code during the Q windows.
Thank you for the perspective.
Corey
Updated
Irma’s Answer
A good rule of thumb is to take a break every 45-60 minutes; the break could be 10-15 minutes. It is a good practice to stretch during your break and you can also go outside, be in contact with nature or like you said, do something you like. You can use a timer to remind you to take a break and to go back to work. Hope this helps :).
Thank you, Irma!
Corey
John Easton CEng FIET FBCS CITP
Design large computer systems for companies
35
Answers
Winchester, England, United Kingdom
Updated
John’s Answer
Hi Corey!
Two thoughts here.
1. I think this depends on your personality. I know some people that want to focus on one thing only without distractions and they will just plough through regardless. Personally, I need "distractions" so while I will spend time on one task, I will frequently change to work on something different (I have lots of parallel projects and clients at once so there is always something else to do). I might not take a break to actually relax, but I will certainly go and work on a different thing for a while and then come back to whatever task needs my attention next.
2. Forget programming. I think that this sort of "taking a break" or "doing something different" is important whatever sort of job you have. I think that unless you are the sort of individual who really can focus properly on one thing, everyone after a while starts to find their mind wandering and that is the time that you need to either take a break or do something different for a while.
Let me also introduce you to a concept called flow. When you have this, time just passes because you are so engaged with what you are doing, you don't notice. If you can get into a flow state, that is great and really productive, but it can be hard to do. Key to doing that is having a task that is interesting / doing things you enjoy.
Hope that helped?
Two thoughts here.
1. I think this depends on your personality. I know some people that want to focus on one thing only without distractions and they will just plough through regardless. Personally, I need "distractions" so while I will spend time on one task, I will frequently change to work on something different (I have lots of parallel projects and clients at once so there is always something else to do). I might not take a break to actually relax, but I will certainly go and work on a different thing for a while and then come back to whatever task needs my attention next.
2. Forget programming. I think that this sort of "taking a break" or "doing something different" is important whatever sort of job you have. I think that unless you are the sort of individual who really can focus properly on one thing, everyone after a while starts to find their mind wandering and that is the time that you need to either take a break or do something different for a while.
Let me also introduce you to a concept called flow. When you have this, time just passes because you are so engaged with what you are doing, you don't notice. If you can get into a flow state, that is great and really productive, but it can be hard to do. Key to doing that is having a task that is interesting / doing things you enjoy.
Hope that helped?
Thank you so much, John!
Corey
Updated
Nancy’s Answer
Maybe I'm reading too much into your question, but I think you might be wondering about the number of breaks allowed in a programming job. Let me shed some light on that.
In the US, computer programming is typically classified as an "exempt" job, which means it's not subject to overtime pay. Basically, it's not about the number of hours you work, but rather how much you accomplish. There aren't any set break times, so you're free to take a break whenever you feel the need. Your productivity is often measured against your colleagues, and this is what sets you apart when it comes to getting raises and promotions. While this might make the environment seem competitive, remember that programming often requires teamwork for larger projects. So, your ability to work well within a team is another factor that can help you stand out for promotions and raises.
When you're job hunting, be sure to consider the team structure of the potential job and how your personal need for breaks fits into their daily routine. Pay attention to how the team's break habits integrate into their workflow without hampering productivity.
In the US, computer programming is typically classified as an "exempt" job, which means it's not subject to overtime pay. Basically, it's not about the number of hours you work, but rather how much you accomplish. There aren't any set break times, so you're free to take a break whenever you feel the need. Your productivity is often measured against your colleagues, and this is what sets you apart when it comes to getting raises and promotions. While this might make the environment seem competitive, remember that programming often requires teamwork for larger projects. So, your ability to work well within a team is another factor that can help you stand out for promotions and raises.
When you're job hunting, be sure to consider the team structure of the potential job and how your personal need for breaks fits into their daily routine. Pay attention to how the team's break habits integrate into their workflow without hampering productivity.
Thank you for giving me advice.
Corey
Updated
Anthany’s Answer
I take breaks often while coding and I think everyone should! It's very easy to get frustrated when coding because, as i'm sure you know, any little mistake can cause your entire code to not work. I've found that whenever I do get frustrated and try to fix whatever was causing the issue, i more often than not will completely over look it whereas when I step away and take a break, i've found that it's a lot easier to find what my mistake was, which tends to be something small like an extra period, and fix it right away!