I write code fueled by coffee for data analysis and automation at a humanitarian agency. Interested in traveling, data science, and data analysis. Love working with Python, SQL and R.
Setting focus hours would help, combined with 40 min work, 20 min break or whichever intervals suit your concentration span the best.
Setting your devices on silent or do not disturb, and focusing on the thing in front of you would help. Noting that too much focus will ruin you mind as you need a mental break, specially if you are stuck with an issue.
Finally, dedicating a certain space/desk for productivity only, this will train your mind to get into work mode while you are there.
I definitely agree with setting up focus hours but also setting up realistic endpoint targets. For example, I want to complete this function, method, class, etc...and it will do this before my next break. I've been guilty of coding to the point of pure exhaustion/frustration that sometimes it's hard to get back to focusing.
Setting focus hours would help, combined with 40 min work, 20 min break or whichever intervals suit your concentration span the best.
Setting your devices on silent or do not disturb, and focusing on the thing in front of you would help. Noting that too much focus will ruin you mind as you need a mental break, specially if you are stuck with an issue.
Finally, dedicating a certain space/desk for productivity only, this will train your mind to get into work mode while you are there.
Great Lara
Thanks
I definitely agree with setting up focus hours but also setting up realistic endpoint targets. For example, I want to complete this function, method, class, etc...and it will do this before my next break. I've been guilty of coding to the point of pure exhaustion/frustration that sometimes it's hard to get back to focusing.
Hmmm
Thanks