3 ms·

As an Army Reservist who has deployed 5 times I have had to make the mental switch, though this is more like extreme switching on/off your entire life. Here is

As an Army Reservist who has deployed 5 times I have had to make the mental switch, though this is more like extreme switching on/off your entire life. Here is my limited coping strategy as it relates only to minor task delegation: * 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. * Anticipate the switch and plan your day/time to accommodate change. The switch to a different task is the easy part. It is building the necessary focus a given task requires that is hard. Know that and plan accordingly so that stress and interference are lower. * when it comes to automating this stress away embrace the stress state directly and make notes about it. Use those notes to identify repeated problems and delays. Solve not for the stress but for the repetition. * I cannot provide guidance for dealing with the emotion or mental stress directly as my situation is a bit more extreme.

tra3 6y ago
> As an Army Reservist who has deployed 5 times I have had to make the mental switch, though this is more like extreme switching on/off your entire life. This must be very tough, thanks for sharing. > * 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. A special, limited case of this is ending your workday. While you're in the zone, and wrapping up your day set yourself up for success by preplanning your next action. If you're coding something and just committed your day's last checkin, write a quick sentence indicating what you're going to be working on tomorrow. When I am able to do this, regaining context next day is much simpler and easier for me.
robertohanas 6y ago
>As an Army Reservist who has deployed 5 times I have had to make the mental switch, though this is more like extreme switching on/off your entire life. Here is my limited coping strategy as it relates only to minor task delegation Thanks for sharing, I hope they didn't take a tool on you. > It is building the necessary focus a given task requires that is hard. Would love if you could explain further this. > I cannot provide guidance for dealing with the emotion or mental stress directly as my situation is a bit more extreme Shit man, I imagine it must not be easy.
flukus 6y ago
> 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.

tra3 6y ago

> As an Army Reservist who has deployed 5 times I have had to make the mental switch, though this is more like extreme switching on/off your entire life. This must be very tough, thanks for sharing. > * 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. A special, limited case of this is ending your workday. While you're in the zone, and wrapping up your day set yourself up for success by preplanning your next action. If you're coding something and just committed your day's last checkin, write a quick sentence indicating what you're going to be working on tomorrow. When I am able to do this, regaining context next day is much simpler and easier for me.

robertohanas 6y ago

>As an Army Reservist who has deployed 5 times I have had to make the mental switch, though this is more like extreme switching on/off your entire life. Here is my limited coping strategy as it relates only to minor task delegation Thanks for sharing, I hope they didn't take a tool on you. > It is building the necessary focus a given task requires that is hard. Would love if you could explain further this. > I cannot provide guidance for dealing with the emotion or mental stress directly as my situation is a bit more extreme Shit man, I imagine it must not be easy.

flukus 6y ago

> 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.