flancian/garden
0
0
Fork 0
mirror of https://github.com/flancian/garden.git synced 2026-07-31 11:36:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

Auto saved by Logseq

Browse Source
This commit is contained in:
Flancian
2022-02-20 15:30:11 +01:00
parent e7bf3622f4
commit 4d9a4dee0a
2 changed files with 19 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files
getting things done.md
+18 -22
View File
@@ -1,22 +1,18 @@
# Getting Things Done
- [[GTD]] for short. A [[productivity]] method by [[David Allen]].
- It's also a book, which I haven't read; [[Luciana]] has.
- [[go]] https://hamberg.no/gtd
- The gist of it:
- Break down tasks. Be specific.
- When go through your backlog, like any inbox (including a "main" one, your base field of operations for executing the GTD algorithms), you try to either take any needed action immediately (but only if it's short; perhaps set a threshold in seconds, rather than minutes) or classify for later doing.
- My take: as I can, I try to expand items, breaking them down into simpler actions and tagging them (classifying them) with a greater degree of specificity. This makes the tasks more tractable over time.
- You classify according to [[time]] and [[context]] for the task of doing. Some example tags:
- [[next action]], [[next week]], [[some day]], [[office]], [[home]], [[project]].
- [[next action]] is where a lot of the magic happens. At some point something needs to be your [[next action]] to get done :)
- I'm trying using [[Getting Things Done]] in the [[Agora]]:
- Actions are wikilinks (I don't distinguish between links and tags; they're all just nodes).
- [[read]], [[research]], [[write]].
- [[next action]].
- [[dome day]].
- [[agora plan]].
- [[do]] acts as an index/root node of the GTD system; whenever I don't know what to do, I just visit [[do]] :)
- a [[technique]].
- [[GTD]] for short. A [[productivity]] method by [[David Allen]].
- It's also a book, which I haven't read; [[Luciana]] has.
- [[go]] https://hamberg.no/gtd
- The gist of it:
- Break down tasks. Be specific.
- When go through your backlog, like any inbox (including a "main" one, your base field of operations for executing the GTD algorithms), you try to either take any needed action immediately (but only if it's short; perhaps set a threshold in seconds, rather than minutes) or classify for later doing.
- My take: as I can, I try to expand items, breaking them down into simpler actions and tagging them (classifying them) with a greater degree of specificity. This makes the tasks more tractable over time.
- You classify according to [[time]] and [[context]] for the task of doing. Some example tags:
- [[next action]], [[next week]], [[some day]], [[office]], [[home]], [[project]].
- [[next action]] is where a lot of the magic happens. At some point something needs to be your [[next action]] to get done :)
- I'm trying using [[Getting Things Done]] in the [[Agora]]:
- Actions are wikilinks (I don't distinguish between links and tags; they're all just nodes).
- [[read]], [[research]], [[write]].
- [[next action]] -> [[do]]
- [[some day]].
- [[agora plan]].
- [[do]] acts as an index/root node of the GTD system; whenever I don't know what to do, I just visit [[do]] :)
journal/2022_02_20.md
+1 -1
View File
@@ -3,4 +3,4 @@
- liking [[dan dennett]]'s [[darwin's dangerous idea]] a lot.
- #push [[do]]
- LATER I am supposed to complete a [[nccr]] survey at some point in time.
- [[getting things done]] has lots of interesting notes
- [[getting things done]] has lots of interesting notes by two other users