mirror of
https://github.com/foo-dogsquared/wiki.git
synced 2025-01-31 04:58:21 +00:00
Update more notes on note-taking
This commit is contained in:
parent
7139ee4f17
commit
b999f3a114
@ -3,7 +3,7 @@
|
||||
:END:
|
||||
#+title: Note-taking
|
||||
#+date: "2020-04-15 14:35:55 +08:00"
|
||||
#+date_modified: "2021-05-09 18:24:13 +08:00"
|
||||
#+date_modified: "2021-05-17 08:28:46 +08:00"
|
||||
#+language: en
|
||||
|
||||
|
||||
@ -17,4 +17,7 @@ There are different ways of note-taking.
|
||||
Among the endless list of methods, popular methods include [[id:4259636e-e0e8-49e4-8210-758ec59728a3][Zettelkasten]], [[id:24b5e144-dda4-482c-9684-958a00d6c986][Roam Research]], Cornell method, or the traditional [[id:d3fbdb1a-9629-45ef-9f08-32c6e49025bb][Linear notes]].
|
||||
|
||||
When doing something like this, one could take notes how to make their notes interesting to read.
|
||||
One could start to [[id:d024516b-35ea-40ae-9433-ceacea695073][Write paragraphs like music]], create notes with [[id:79357d56-74bf-4854-820c-c0ad849f2468][Classic prose]], and [[id:b318dc2b-5fa1-48ff-9d33-6fbbdee46a2f][Write down the simplest possible example]].
|
||||
One could start to [[id:d024516b-35ea-40ae-9433-ceacea695073][Write paragraphs like music]], create notes with [[id:79357d56-74bf-4854-820c-c0ad849f2468][Classic prose]], [[id:b318dc2b-5fa1-48ff-9d33-6fbbdee46a2f][Write down the simplest possible example]], and [[id:b0aee2c6-f759-4b7a-829f-79781926091e][Create examples of ranking complexity when documenting your project]].
|
||||
|
||||
Not all note-taking is the formal method of paraphrasing our observations and thoughts, this can also be a method of merely writing our thoughts down.
|
||||
We can [[id:810dc8b6-db64-4c80-a0aa-f9e6d5fa4acf][Create an inbox to store your thoughts]], create [[id:3d1c0313-fa3d-4b18-b435-51d3837e3e2c][Fleeting notes]] as a mental scratchpad.
|
||||
|
@ -3,7 +3,7 @@
|
||||
:END:
|
||||
#+title: Write down the simplest possible example
|
||||
#+date: "2020-06-27 18:31:40 +08:00"
|
||||
#+date_modified: "2021-05-13 16:17:27 +08:00"
|
||||
#+date_modified: "2021-05-17 08:26:35 +08:00"
|
||||
#+language: en
|
||||
|
||||
|
||||
@ -11,6 +11,8 @@ On practice, writing down the simplest possible examples allows you to get start
|
||||
When you're done with the simplest possible example, you can slowly amp the complexity until you worked your way to a real mind-boggling example that really made you bang your head to a wall.
|
||||
As they say, [[id:05a39f96-fb1c-4d71-9be1-fc4c2e251e8f][Start small and improve later]].
|
||||
|
||||
As a sidenote, it is also helpful to [[id:b0aee2c6-f759-4b7a-829f-79781926091e][Create examples of ranking complexity when documenting your project]] from your research or leisure studies.
|
||||
|
||||
On the non-practical side, it is said to be a cultural thing for mathematicians.
|
||||
It is an unwritten rule for a reader to immediately write down examples and not pass through the text until they have understood it.
|
||||
Providing examples is not an obligation from the author but they may do so for the sake of easier understanding.
|
||||
|
@ -3,14 +3,17 @@
|
||||
:END:
|
||||
#+title: Create examples of ranking complexity when documenting your project
|
||||
#+date: "2021-02-28 14:52:58 +08:00"
|
||||
#+date_modified: "2021-05-07 14:18:19 +08:00"
|
||||
#+date_modified: "2021-05-17 08:57:48 +08:00"
|
||||
#+language: en
|
||||
|
||||
|
||||
Some projects such as user applications should include examples of usage varying of the complexity from a simple "Hello world"-esque example to a real-life example that the developer uses.
|
||||
This gives a quick introduction to the tool as well as subtly giving hints about what you can do with the program.
|
||||
Some projects such as user applications include examples of usage varying of the complexity from a simple "Hello world"-esque example to a real-life example that the developer uses.
|
||||
This acts as a quick introduction to the project as well as subtly giving hints about what you can do with the program.
|
||||
Examples include the manual pages from [[https://www.freebsd.org/][the FreeBSD project]] where each tool is given a dedicated section for example usage.
|
||||
Another that stuck out to me is the README of [[https://github.com/naelstrof/maim/tree/b1b28fcb0c3a44e699fd879189316440b7edff22][maim]], a screenshot capture tool, where one of the examples demonstrate that you can pipe binary output which leads to useful things such as [[https://github.com/naelstrof/maim/tree/b1b28fcb0c3a44e699fd879189316440b7edff22][OCR selection]] or a colorpicker.
|
||||
|
||||
Practicing this in your studies is also helpful, creating a primer of the topic that you can refer to.
|
||||
You can then break the examples down and include it in a [[id:063dfd73-dbf5-437b-b6f1-d7aeca196f31][Spaced repetition]] session (e.g., include the examples in Anki).
|
||||
|
||||
This is not only useful for software documentation, it is also useful for technical writings.
|
||||
This makes it easier to skim (see [[id:5c1e9540-9663-4512-8c84-05529ad22212][Speedreading is all about skimming well]]) and to [[id:9a11ef31-b2a7-43a9-a7a9-48f191838c6e][Prefer referencing over remembering]].
|
||||
|
@ -3,16 +3,16 @@
|
||||
:END:
|
||||
#+title: Understanding comes first from memory
|
||||
#+date: "2021-05-14 11:48:20 +08:00"
|
||||
#+date_modified: "2021-05-14 12:55:29 +08:00"
|
||||
#+date_modified: "2021-05-17 08:53:22 +08:00"
|
||||
#+language: en
|
||||
|
||||
|
||||
Rote learning is often considered to be an inferior method of understanding a concept.
|
||||
It is often underestimated.
|
||||
You may have often hear something along the lines of "I don't want to memorize a bunch of facts but rather understand the process." or "Knowing something is different from understanding something.";
|
||||
rooted from an experience of bad teaching thus we associate memorizing a bunch of facts as bad.
|
||||
it is rooted from an experience of bad teaching thus we associate memorizing a bunch of facts as bad.
|
||||
|
||||
Knowing the related things — or memorizing a bunch of facts — is a good way to understand a concept.
|
||||
Knowing the related things — or memorizing a bunch of facts — is a good way to start learning a concept.
|
||||
With those things in mind, you can then combine the ideas, [[id:1e135aee-0464-4756-9f55-bbf12afe8254][Chunking]] them, and innovate new ones.
|
||||
You cannot build upon more ideas if you don't know what those ideas are.
|
||||
|
||||
|
@ -3,16 +3,19 @@
|
||||
:END:
|
||||
#+title: Information is only acquired when you try to make sense of it
|
||||
#+date: "2021-05-14 12:15:54 +08:00"
|
||||
#+date_modified: "2021-05-14 13:02:45 +08:00"
|
||||
#+date_modified: "2021-05-17 08:56:27 +08:00"
|
||||
#+language: en
|
||||
|
||||
|
||||
# TODO: Improve note
|
||||
No matter how many articles, videos, and images you read, information only stays in the author's intent until you take the time to make sense of it.
|
||||
Information that is absorbed and not applied is just something that we know.
|
||||
And knowing something is different from understanding something.
|
||||
|
||||
- experimentation, trying out through examples, documenting your process
|
||||
- this is the reason why we write notes, document a project, or asking questions to the author
|
||||
- the information will never be 100% of the author's intention
|
||||
- context and environment is just different in subtle ways
|
||||
- just the key ideas are important
|
||||
- reader may lead into different conclusions
|
||||
No matter how many articles, videos, and images you read, information only stays in the author's intent until you take the time to make sense of it.
|
||||
It will never start unless you experiment.
|
||||
One of the simplest way to start is to sit down, [[id:b318dc2b-5fa1-48ff-9d33-6fbbdee46a2f][Write down the simplest possible example]], and work your way through those examples.
|
||||
|
||||
This is also applied when we collect knowledge: collecting books, downloading eBooks, bookmarking articles, and archiving resources.
|
||||
When we never used them, it is just the same as window shopping for that wanted thing except we bought it and just an arm's length away when we want to use it.
|
||||
|
||||
That doesn't mean we should understand every bit of information coming our way.
|
||||
In the end, [[id:864a9242-eb10-44ad-81b7-c237276523e5][We know more compared to what we understood]].
|
||||
|
16
2021-05-17-08-47-37.org
Normal file
16
2021-05-17-08-47-37.org
Normal file
@ -0,0 +1,16 @@
|
||||
:PROPERTIES:
|
||||
:ID: 864a9242-eb10-44ad-81b7-c237276523e5
|
||||
:END:
|
||||
#+title: We know more compared to what we understood
|
||||
#+date: "2021-05-17 08:47:37 +08:00"
|
||||
#+date_modified: "2021-05-17 08:55:57 +08:00"
|
||||
#+language: en
|
||||
|
||||
|
||||
While [[id:114b7874-6a20-49c8-be2c-46970c7110dc][Information is only acquired when you try to make sense of it]], we just know more compared to what we understood.
|
||||
It doesn't mean it's a bad thing as [[id:c0e4fb0e-68f2-4db4-8c3e-f5a7845738c3][Understanding comes first from memory]].
|
||||
The amount of things is too great that deserve our limited attention.
|
||||
|
||||
- we can still make sense since we are more associative than structured
|
||||
- the skill of referencing through can help starting to understand
|
||||
- note-taking can help increase
|
Loading…
Reference in New Issue
Block a user