Context Switching
-
I don't know, but 4 Disciplines of Execution[^] may provide some insights into effective management to deliver goals. This is the book our company gave to all the managers and team leads at our latest operations conference in February.
Reviews look good might give it a go myself, have you read it Dave? What do you think of it?
Simon Lee Shugar (Software Developer) www.simonshugar.co.uk "If something goes by a false name, would it mean that thing is fake? False by nature?" By Gilbert Durandil
-
Reviews look good might give it a go myself, have you read it Dave? What do you think of it?
Simon Lee Shugar (Software Developer) www.simonshugar.co.uk "If something goes by a false name, would it mean that thing is fake? False by nature?" By Gilbert Durandil
Not read it thoroughly, have it on my desk though (at home!)....:~ They do focus on Wildly Important Goals (WIGs), although I'm happy with my baldy head, each of the managers in the company has to have 2 WIGs, and each 2 persons WIGs must be able to talk directly to/influence their immediate bosses 2 WIGS etc. all the way up the chain. It does make you focus more and make sure you make an effort on the critically important stuff rather than getting caught up in the whirlwind of the day to day stuff.
-
I don't know, but 4 Disciplines of Execution[^] may provide some insights into effective management to deliver goals. This is the book our company gave to all the managers and team leads at our latest operations conference in February.
-
Conext Switching is a massive part of coding / development / engineering and managing. I have wondered if there should be a book written out there, for management staff, that highlights the dangers of too much context switching in your employees schedule. So an easy example of this is your working on a medium to long term project and something of high priority comes up and you've got to switch on to it. Spending a few hours or more on this high priority project means you have lost all of the context to the original project, the variables, designs and implementation all your plans ruined. You switch back to the original and now have to take the time to build up that context again. Drives me mad, anyway does anyone have any techniques for clearing their head between tasks / context switching? Between tasks or projects I close everything down, every window, notepad, IDE, browser etc until I've got my basic windows which enable me to start a new project. This ritual makes me feel like I'm "clearing" the context of previous work from my mind.
Simon Lee Shugar (Software Developer) www.simonshugar.co.uk "If something goes by a false name, would it mean that thing is fake? False by nature?" By Gilbert Durandil
Well may be you will be used to it if that is frequently happen to you. in my current company i always work on two or three project together and among them one of the project i am handling from last 2 years. initially it will give you some headache but later on you will be used to it. you can always divide your task based on priority. :thumbsup::thumbsup:
Ravi Khoda
-
Conext Switching is a massive part of coding / development / engineering and managing. I have wondered if there should be a book written out there, for management staff, that highlights the dangers of too much context switching in your employees schedule. So an easy example of this is your working on a medium to long term project and something of high priority comes up and you've got to switch on to it. Spending a few hours or more on this high priority project means you have lost all of the context to the original project, the variables, designs and implementation all your plans ruined. You switch back to the original and now have to take the time to build up that context again. Drives me mad, anyway does anyone have any techniques for clearing their head between tasks / context switching? Between tasks or projects I close everything down, every window, notepad, IDE, browser etc until I've got my basic windows which enable me to start a new project. This ritual makes me feel like I'm "clearing" the context of previous work from my mind.
Simon Lee Shugar (Software Developer) www.simonshugar.co.uk "If something goes by a false name, would it mean that thing is fake? False by nature?" By Gilbert Durandil
This is something I struggle with. I think software needs a great deal of focus, so switching from one project to another I find difficult. When I get to the point that I'm doing about 5 things at once, overall progress comes to pretty much a standstill. You have to start writing things down, as you'll never remember everything. Thread local storage, as it were. There are only two things I can suggest - firstly be prepared to say no to whoever is asking for stuff and secondly don't let it stress you out (activate your "don't care" gene..) I don't smoke any more, but stepping out the office used to be good when things were getting too much. Have you thought of taking up smoking/smoking more? *EDIT* That's probably bad advice.
Regards, Rob Philpott.
-
This is something I struggle with. I think software needs a great deal of focus, so switching from one project to another I find difficult. When I get to the point that I'm doing about 5 things at once, overall progress comes to pretty much a standstill. You have to start writing things down, as you'll never remember everything. Thread local storage, as it were. There are only two things I can suggest - firstly be prepared to say no to whoever is asking for stuff and secondly don't let it stress you out (activate your "don't care" gene..) I don't smoke any more, but stepping out the office used to be good when things were getting too much. Have you thought of taking up smoking/smoking more? *EDIT* That's probably bad advice.
Regards, Rob Philpott.
I am afraid I could never smoke but having a walk might be another idea. I am using whiteboards at the moment... to manage a lot of projects. Going home with a head ache each day I try to shut my brain down to a minimum during the commute home, which might also be bad advice!
Simon Lee Shugar (Software Developer) www.simonshugar.co.uk "If something goes by a false name, would it mean that thing is fake? False by nature?" By Gilbert Durandil
-
Conext Switching is a massive part of coding / development / engineering and managing. I have wondered if there should be a book written out there, for management staff, that highlights the dangers of too much context switching in your employees schedule. So an easy example of this is your working on a medium to long term project and something of high priority comes up and you've got to switch on to it. Spending a few hours or more on this high priority project means you have lost all of the context to the original project, the variables, designs and implementation all your plans ruined. You switch back to the original and now have to take the time to build up that context again. Drives me mad, anyway does anyone have any techniques for clearing their head between tasks / context switching? Between tasks or projects I close everything down, every window, notepad, IDE, browser etc until I've got my basic windows which enable me to start a new project. This ritual makes me feel like I'm "clearing" the context of previous work from my mind.
Simon Lee Shugar (Software Developer) www.simonshugar.co.uk "If something goes by a false name, would it mean that thing is fake? False by nature?" By Gilbert Durandil
Have a separate (physical) notebook or at least sections in a notebook for the different projects, so you have some place that you write down 'context' so you can come back to it. If the projects don't require the same software, or you can start multiple instances, I like to leave all the windows for everything I'm working on open. Minimise the ones you don't care about but leave them open so when you switch back to that project, all the context is just as you left it. You could even use VMs, one per project, to get really good separation without complete loss of project context.
-
Conext Switching is a massive part of coding / development / engineering and managing. I have wondered if there should be a book written out there, for management staff, that highlights the dangers of too much context switching in your employees schedule. So an easy example of this is your working on a medium to long term project and something of high priority comes up and you've got to switch on to it. Spending a few hours or more on this high priority project means you have lost all of the context to the original project, the variables, designs and implementation all your plans ruined. You switch back to the original and now have to take the time to build up that context again. Drives me mad, anyway does anyone have any techniques for clearing their head between tasks / context switching? Between tasks or projects I close everything down, every window, notepad, IDE, browser etc until I've got my basic windows which enable me to start a new project. This ritual makes me feel like I'm "clearing" the context of previous work from my mind.
Simon Lee Shugar (Software Developer) www.simonshugar.co.uk "If something goes by a false name, would it mean that thing is fake? False by nature?" By Gilbert Durandil
Simon Lee Shugar wrote:
you have lost all of the context to the original project, the variables, designs and implementation all your plans ruined.
That's usually a sign of two things for me: 1. If I was in some process where I needed to keep a mental stack of all this stuff, then I should finish the process. Very few "high priority" projects ever actually live up to their name, and yes, it'll piss off the manager, which is why I work for myself, because at least then there's only one idiot making decisions, not a corporation full of them. :) 2. And more relevant, just like the idea of keeping your functions small, if I'm dealing with a large stack in my head, it usually means that the code is bad. It's actually one of my "red flags" warning signs -- the code is too entangled, the process / workflow / whatever is too complex and not easily understood, and so forth. When that happens, I take a step back and ask myself, "how would I change the code so that it's not such a mental effort to work with it?" and the result is usually much, much better code. Of course, neither #1 or #2 are carved in stone, but they are at signposts along the road to hell that I try to pay attention to. Marc
-
Conext Switching is a massive part of coding / development / engineering and managing. I have wondered if there should be a book written out there, for management staff, that highlights the dangers of too much context switching in your employees schedule. So an easy example of this is your working on a medium to long term project and something of high priority comes up and you've got to switch on to it. Spending a few hours or more on this high priority project means you have lost all of the context to the original project, the variables, designs and implementation all your plans ruined. You switch back to the original and now have to take the time to build up that context again. Drives me mad, anyway does anyone have any techniques for clearing their head between tasks / context switching? Between tasks or projects I close everything down, every window, notepad, IDE, browser etc until I've got my basic windows which enable me to start a new project. This ritual makes me feel like I'm "clearing" the context of previous work from my mind.
Simon Lee Shugar (Software Developer) www.simonshugar.co.uk "If something goes by a false name, would it mean that thing is fake? False by nature?" By Gilbert Durandil
A good read (for any manager): Human Task Switches Considered Harmful[^] /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
Have a separate (physical) notebook or at least sections in a notebook for the different projects, so you have some place that you write down 'context' so you can come back to it. If the projects don't require the same software, or you can start multiple instances, I like to leave all the windows for everything I'm working on open. Minimise the ones you don't care about but leave them open so when you switch back to that project, all the context is just as you left it. You could even use VMs, one per project, to get really good separation without complete loss of project context.
BobJanova wrote:
If the projects don't require the same software, or you can start multiple instances, I like to leave all the windows for everything I'm working on open. Minimise the ones you don't care about but leave them open so when you switch back to that project, all the context is just as you left it. You could even use VMs, one per project, to get really good separation without complete loss of project context.
This is where something like Sysinternal's Desktops[^] can come in handy.
-
Conext Switching is a massive part of coding / development / engineering and managing. I have wondered if there should be a book written out there, for management staff, that highlights the dangers of too much context switching in your employees schedule. So an easy example of this is your working on a medium to long term project and something of high priority comes up and you've got to switch on to it. Spending a few hours or more on this high priority project means you have lost all of the context to the original project, the variables, designs and implementation all your plans ruined. You switch back to the original and now have to take the time to build up that context again. Drives me mad, anyway does anyone have any techniques for clearing their head between tasks / context switching? Between tasks or projects I close everything down, every window, notepad, IDE, browser etc until I've got my basic windows which enable me to start a new project. This ritual makes me feel like I'm "clearing" the context of previous work from my mind.
Simon Lee Shugar (Software Developer) www.simonshugar.co.uk "If something goes by a false name, would it mean that thing is fake? False by nature?" By Gilbert Durandil
My rule is, if it isn't on fire, it can wait for a few minutes/hours/days until I reach a good stopping point in my current task. I then make notes sufficient to remind me of what I was doing, where, and why, and then switch.
Software Zen:
delete this;
