Answer by Arkaaito for What to do about "next piece syndrome"?
I keep a list of non-urgent tasks (update this wiki page, refactor this class, write some basic unit tests for this other tasks, do code reviews for X Y and Z...), with associated ballpark estimates....
View ArticleAnswer by user8709 for What to do about "next piece syndrome"?
How important is the clock to your employer?The simple answer may be to sometimes start the new task and see it through, finishing late as a result, but sometimes just leave early. So long as you're...
View ArticleAnswer by JB King for What to do about "next piece syndrome"?
There is also something to be said for where in your schedule are you at this point. For example, on a Friday afternoon I may pick quite a different option than I would on a Tuesday or Wednesday where...
View ArticleAnswer by Bryan M. for What to do about "next piece syndrome"?
Find a simple task you can do that does take a half hour or less. Update some documentation, refactor a test or two, fiddle with your dev environment config, or shoot off a few emails.Basically, there...
View ArticleAnswer by Robert Harvey for What to do about "next piece syndrome"?
Start working on the next piece. When it's time to wrap up, find a logical place to stop (the last line of code, perhaps), save your work, write a brief note reminding yourself where you are and what...
View ArticleWhat to do about "next piece syndrome"?
Inspired by this question:What to do about "stopping point syndrome"?I often find myself a half hour away from knocking-off time having just wrapped up a component of my work, and facing a "next piece"...
View Article
