3 ms·
I’ve never thought GTD is a good system for programmers. The last thing I want to do is interrupt some important piece of work because an incoming request will
by tonyedgecombe 2y ago
I’ve never thought GTD is a good system for programmers. The last thing I want to do is interrupt some important piece of work because an incoming request will only take a couple of minutes.
- scubbo 2y agoThat's entirely contrary to my understanding and implementation of GTD - which is to have daily "scans" of my inboxes to see what tasks have come in since the last scan, bucket them into the appropriate categories/lists/record-keeping systems, and then _close those inboxes_ until the next scan. If anything, GTD keeps me _more_ interruption-free, by strictly ringfencing the times that I am open to processing new task-requests.
- andai 2y agoI assume you're referring to the 2 minute rule here. One of the main points of GTD is that you can just make a note of the interruption, so you don't have to deal with it right then, because you know it's waiting for you in a trusted system. (Which incidentally might just be a sticky note on your desk!) Also, the 2 minute rule itself is flexible, just like the rest of the system. Sometimes it's a 30 second rule, and sometimes it's a 5 minute rule.