capture

This is a process to deal with scenarios where:

• you are reading an article
• you find a term that you don’t know what’s it about

The process is follows: when you spot a term, like “RNN”, that you have no idea what it is:

1. put “What is RNN” into global capture place, together with a link to the context of the material (the reference note, if it is a paper)
2. ignore “RNN” and continue processing the material

Then, in the capture processing, process it same as other capture ideas(if can be done within 3 minute, do it, if not, schedule a task to do it)

This is a process to deal with scenarios where:

• you are reading an article
• you find a term that you don’t know what’s it about

The process is follows: when you spot a term, like “RNN”, that you have no idea what it is:

1. put “What is RNN” into global capture place, together with a link to the context of the material (the reference note, if it is a paper)
2. ignore “RNN” and continue processing the material

Then, in the capture processing, process it same as other capture ideas(if can be done within 3 minute, do it, if not, schedule a task to do it)

A note of capture should be:

cover all

note everything thought of So the entirety of it could be forgot and dumped out of mind

verbose

include example, context, reference, so that it make sense after 1 day or 2

sentence where possible

an complete idea with ground and , not only being aware of an entity(however the awareness itself sometime is powerful enough)

atomic where possible

when idea comes one after another, try make them seperate remarks and one large one including them. looks like zettel; flexible, easier to process and review; easier to write, few more C-c ENT and a lot less words/justification/speculation

• on Herman’s systems:
  • I simplified most existing things:
    • capture - I now use one capture inbox for everything: task, ideas, bookmark, so GTD capture and research capture are combined. This is a practice, not to say it is good or bad, it is simple enough to work decently
    • review - I now review my zettelkasten daily, but sometimes there’s more than what I can do on the instant.(like the whole of my research system is like a big pile of nonsense right now, and so is my GTD integration; I’ll reduce, or delete them entirely very shortly after)
    • tags - I don’t use it as of now. I may start it somewhere in the future, but now I don’t use it
    • process - One process diagram should be enough, instead of this giant load of text
    • engage - checking agenda, and that’s it. I use phone timer more often now.
  • in general, this whole page is very not useful. I use current life script more now, although it does not contain information on research and stuff. I could extend it to include these though.
  • I use some new concepts, like primitive action, and new set of very limited primitives in top of my mind.
  • I practice slow-carb diet and use a fitness program now, they should be included.
  • It is decided: I’m stuffing everything in the lifestyle script. research is a lifestyle, fitness is a lifestlye, shake the staticity off is a lifestyle, I live and I live with a style. Yet I may want to have it split into smaller pieces
• on the zettelkasten
  • lots of places for reduction and improvement it is not very useful in general. old, rambling note that should be discarded in second batch processing are scattering at places where I quote them, thinking they are good concise notes. A lot of places could use visuals and concise words, examples or links to concrete examples
• on the tasks
  • the reduction is working, there’s a lot to think for the tasks. this means a change to the my GTD zettel is in request
• on tracking and experiments
  • tracking is hard to remember. but it is damn useful.
  • highlight + comment method and capture is a form of tracking thoughts
  • so I think I should track some specific, explicitly measureable things, and have them noted somewhere so I don’t forget