> Keep good notes. Be better prepared to jump back into a different task by knowing exactly where you left off, problem state, and what the next step is. To ex

> Keep good notes. Be better prepared to jump back into a different task by knowing exactly where you left off, problem state, and what the next step is. To expand on this (and point 3), there's some non-obvious (to many) types of notes that can help you switch: * Sql snippets to display/manipulate the data. * Log snippets with relevant stack traces. * Debugger breakpoints and core dumps (if applicable), can be scripted on the command line or imported/exported from the IDE. Don't forget debuggers are scriptable too, most devs use a fraction of a debuggers power. * Custom scripts, like something that can grep logs for the specific issue you're working on, toggle config settings, setup data in a specific way, etc. These can help you immediately jump back to the problem rather than jumping to the project and then working your way back to the problem. They don't always help, but more often you'll be able to switch in 5 minutes rather than 4 hours. They will also help with notes to QA and support along with documentation.