4 ms·

I wish something like that would work for me. I would immediately begin to analyse what counts as a task. I'd set myself tasks, realise they're much more diffic

I wish something like that would work for me. I would immediately begin to analyse what counts as a task. I'd set myself tasks, realise they're much more difficult than I thought they were and realise there's no way for me to complete this task and also hit my 25 goal. Then I'd get frustrated with myself and probably go surf reddit for the rest of the day. No system of any type has worked for me consistently.

taeric 6y ago
I feel you on this. I have found that no system lasts for me. I have also found that any system can help to get me going. Such that now I try not to use anything to plan his things will end, but only how I will begin them. Similar problems hit me with exercise. About the only system I have there is too obligate myself to finish something. For example, if I walk the dog a mile out, I have to walk the mile in, as well. Bike to work? I have to bike home now.
Shugarl 6y ago
I also tend to overanalyze things, but books like "Atomic Habits" and "The Slight Edge" were really helpful. It made realize that there's no point to try to properly define what a task is, as what I can do at any given day depends on my physical and mental state. How I perform when I have a bad day is completely different from my performance on a good day. Something that's a task today might not be considered like one tomorrow. There'll be days where I'll only do 25 small things then call it a day, and that's okay.
webmaven 6y ago
> I wish something like that would work for me. I would immediately begin to analyse what counts as a task. I'd set myself tasks, realise they're much more difficult than I thought they were and realise there's no way for me to complete this task and also hit my 25 goal. Can you permit yourself to subdivide those tasks that turn out to be more difficult?
- taeric 6y ago
  Subdividing in total doesn't work for me. Unless it is something I already know how to do. Identifying the next thing works ok.
  - webmaven 6y ago
    So, if something is taking longer because you're identifying previously unanticipated subtasks, does doing the yak-shaving count toward your count of tasks, or not?
    - taeric 6y ago
      Ha! Sadly, no. Fidling with the editor is never really the next thing. I have had brew mess up things before, such that fixing it is. I used to have an hour or so a week where I would consider what I called process improvement. And if anything ever really slows me down, I do consider that a priority.
      - webmaven 6y ago
        I meant more along the lines of tracking an issue through transitive dependencies, and then having to make a change at each step before the fix is apparent in the code you were actually writing. I once found a weird import issue in a Google App Engine demo that, IIRC, traced back through to pip, virtualenv, and eventually setuptools.

taeric 6y ago

I feel you on this. I have found that no system lasts for me. I have also found that any system can help to get me going. Such that now I try not to use anything to plan his things will end, but only how I will begin them. Similar problems hit me with exercise. About the only system I have there is too obligate myself to finish something. For example, if I walk the dog a mile out, I have to walk the mile in, as well. Bike to work? I have to bike home now.

Shugarl 6y ago

I also tend to overanalyze things, but books like "Atomic Habits" and "The Slight Edge" were really helpful. It made realize that there's no point to try to properly define what a task is, as what I can do at any given day depends on my physical and mental state. How I perform when I have a bad day is completely different from my performance on a good day. Something that's a task today might not be considered like one tomorrow. There'll be days where I'll only do 25 small things then call it a day, and that's okay.

webmaven 6y ago

> I wish something like that would work for me. I would immediately begin to analyse what counts as a task. I'd set myself tasks, realise they're much more difficult than I thought they were and realise there's no way for me to complete this task and also hit my 25 goal. Can you permit yourself to subdivide those tasks that turn out to be more difficult?

taeric 6y ago
Subdividing in total doesn't work for me. Unless it is something I already know how to do. Identifying the next thing works ok.
- webmaven 6y ago
  So, if something is taking longer because you're identifying previously unanticipated subtasks, does doing the yak-shaving count toward your count of tasks, or not?
  - taeric 6y ago
    Ha! Sadly, no. Fidling with the editor is never really the next thing. I have had brew mess up things before, such that fixing it is. I used to have an hour or so a week where I would consider what I called process improvement. And if anything ever really slows me down, I do consider that a priority.
    - webmaven 6y ago
      I meant more along the lines of tracking an issue through transitive dependencies, and then having to make a change at each step before the fix is apparent in the code you were actually writing. I once found a weird import issue in a Google App Engine demo that, IIRC, traced back through to pip, virtualenv, and eventually setuptools.