Essentially you want to make context switching into a task as easy as possible. Some ways to do that are:
. Maintain a list of tasks you can work on, and make it good enough that you can blindly pick one up and start working after a switch.
. Saving context via documentation/text/workspaces as japhyr mentioned helps me a lot. Whenever i come across an issue that i cant handle at that time, i throw it in a text file. At the end of a session, i organize the list. When i come back to task X, i just look at the list and start working on it. Just going through the list, seeing what I did and what remains is the fastest way ive found to warm up and get back in the flow of a project.
. Optimize your workflow. With a tiny chunk of time like this, 5 minutes setting up a workspace or even re-reading an article is too much. So save as much of the workspace as possible, take notes on how article X applies to your project.
. Maintain a list of tasks you can work on, and make it good enough that you can blindly pick one up and start working after a switch.
. Saving context via documentation/text/workspaces as japhyr mentioned helps me a lot. Whenever i come across an issue that i cant handle at that time, i throw it in a text file. At the end of a session, i organize the list. When i come back to task X, i just look at the list and start working on it. Just going through the list, seeing what I did and what remains is the fastest way ive found to warm up and get back in the flow of a project.
. Optimize your workflow. With a tiny chunk of time like this, 5 minutes setting up a workspace or even re-reading an article is too much. So save as much of the workspace as possible, take notes on how article X applies to your project.