How to take fewer breaks to be more productive at work

Click for: original source

Programmer’s work might look easy, but it turns out to be stressful to many programmers. Most programmers would complain about being unproductive — they should work eight hours per day, but these eight hours turn into 2 or 3 hours of work. By Nuha Khaled.

Coding for a long time needs lots of focus, and that causes fatigue, especially when this long focus includes long hours of sitting, analyzing, problem-solving, and just coding! At that point, the programmer feels they can’t reach a solution anymore, can’t focus anymore, and are getting a severe headache.

The article is paying attention to:

  • What everyone recommends?
  • What is an activity break?
  • How can we use it as programmers?

List of example activities for programmer which can be used for acitivity break:

  • Coding
  • Problem analyzing
  • Brainstorming
  • Meetings
  • Planning my working day
  • Responding to emails
  • Writing documents

In brief, we usually are doing a primary activity when working, and to refresh, we just need to take a break from the activity, not from the entire work! Changing the activity alone is not enough if they both have the same method. So, problem-solving might not be a break for you from coding, as both need focusing for example. Good read!

[Read More]

Tags software learning miscellaneous how-to cio