2 ms·
i've always wondered why I eagerly jump in to some big tasks whereas others fill me with anxiety and trigger procrastination, and recently I've come up with a w
by parpfish 1y ago
i've always wondered why I eagerly jump in to some big tasks whereas others fill me with anxiety and trigger procrastination, and recently I've come up with a working theory:
if the task requires requires leaving a stable equilibrium and moving to another, I will procrastinate. So things like "fixing these bugs" or "build a prototype" are fine, but "migrate this system from X to Y" are a problem.
It's because these are the tasks where you know things are going to get worse before they get better.
When I work, I want to fix things and shrink my to-do list (why yes, I am an inbox-zero kind of guy). These big migration tasks are the type of work where once you start, your to-do list gets bigger.
- ElevenLathe 1y agoI tend to like "make the line go down to zero" type tasks (not burndown charts but like "# of integrators with old API"). IMO it feels good to have a solid definition of done and realistically most tasks don't.