2 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 diff
by 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 agoSubdividing 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 agoSo, 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 agoHa! 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 agoI 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.