I think this approach has some rather nice features:
1. There is no need to try and break a task down into smaller steps before entering it into the list. When you come to work on it you probably have had a chance to think about it some more and it will be obvious if there are any sub-tasks.
2. There is no schedule and the granularity is (inifinitely) variable. This helps avoid needless analysis or planning.
3. Garbage-colletion. If you perform a task that invalidates some easlier items on your lists the dismissal process should catch that without having to review or re-analyse the complete list looking for dependencies.
So for a system that is appears free-form and light on rules it actually has some substance. The only issue I can see is one that asimjalis commented on where one task can take too much time. I think that then it is appropriate to wind up the pomodoro.
1. There is no need to try and break a task down into smaller steps before entering it into the list. When you come to work on it you probably have had a chance to think about it some more and it will be obvious if there are any sub-tasks.
2. There is no schedule and the granularity is (inifinitely) variable. This helps avoid needless analysis or planning.
3. Garbage-colletion. If you perform a task that invalidates some easlier items on your lists the dismissal process should catch that without having to review or re-analyse the complete list looking for dependencies.
So for a system that is appears free-form and light on rules it actually has some substance. The only issue I can see is one that asimjalis commented on where one task can take too much time. I think that then it is appropriate to wind up the pomodoro.