dragonwell
Programmer
That's sort of an oxymoron, isn't it? If you're focused on something, naturally you block out all the other stuff. But we need to multi-task. I don't mean multi-tasking as in "walk and chew gum", but in a wider sense like "develop enterprise application A, work on website B, manage servers X,Y,Z, design application C, etc. and get it all done in 6 months." Us programmers are particularly good at concentrating, and that is generally a good thing. But it seems to be a hinderance, too.
My problem is that once I get going on one project, I just want to keep going and going and going until it's "done" and as a result all the other projects that need to get done are neglected. Part of this is due to the nature of IT projects - if you're away from the mental space for any length of time, it can take a significant amount of time just to get yourself up back up to speed and back into exactly where you left off. So for this reason, plans like "ok, work on project 1 for four hours, then stop and work on project 2 for four hours" just don't ever seem to work out.
[blue]_______________________________________[/blue]
"AND when tweetle beetles battle with paddles in a puddle, they call it a tweetle beetle puddle paddle battle AND..."
My problem is that once I get going on one project, I just want to keep going and going and going until it's "done" and as a result all the other projects that need to get done are neglected. Part of this is due to the nature of IT projects - if you're away from the mental space for any length of time, it can take a significant amount of time just to get yourself up back up to speed and back into exactly where you left off. So for this reason, plans like "ok, work on project 1 for four hours, then stop and work on project 2 for four hours" just don't ever seem to work out.
[blue]_______________________________________[/blue]
"AND when tweetle beetles battle with paddles in a puddle, they call it a tweetle beetle puddle paddle battle AND..."