Wednesday, January 1, 2014

[coding] On Productivity: Break Scheduling

I think I just realized a key...element to when I am forced to take a break from programming.  In the past I have described to people an urgent desire to drop my work and leave as soon as I figure something out.  For example, upon discovering the solution of a difficult bug, I would often just walk away from my computer without checking in the fix, or even making the fix, etc.

Related to that, I think, is another cause:  "switching gears."  It may actually be the same task, but when I sort of complete one aspect of it (e.g. "getting the camera working" -- which involves learning the android camera feature) enough that I need to move onto another aspect of the same task (e.g. "saving the picture in the data store" -- which involves refactoring part of the data layer), it is the new task that requires loading up a bunch of different information and classes into my head (working memory?) so that I can work on it.  I think the reason why I feel such a strong urge to take a break is that my mind wants to rest from what I was just working on.  Also, and this is key, I think the break helps to forget everything I was just doing that I don't need to remember (all the camera stuff).

Anyway.  That's the theory.

No comments:

Post a Comment