43 karma · joined May 1, 2016
1. Give a header an id and jump to it from anywhere.
2. Attach scheduling information to the header so that you can easily track TODOs and DONEs. I usually further break down a TODO into several sub-TODOs and write something under each one to organize my thoughts, including code blocks, tables, quotes, footnotes, which is impossible in Markdown.
3. You can attach anything else to it, too. I also attach an Anki note ID to it and use Org Mode as an alternative Anki editing environment. Because of the attached note ID, I can easily distinguish whether I want to create a new Anki card (without an ID) or update an existing one (with an ID). That is also hard to implement in Markdown (Strictly speaking, I don't think it's even possible to implement it in Markdown).
My only complaint is that Emacs is the only text editor that fully supports Org Mode. Other editors (e.g. vim, VSCode) support it too, with only to an extent.
Sometimes I also wonder why Org Mode is not as popular as Markdown, the former is far more powerful.
Sometimes I do use VSCode as an alternative, but VSCode only has a rudimentary implementation of org-mode, and the so-called org-mode alternative - markdown - is not nearly as powerful as org-mode.
1. Explain to yourself how algorithms work, like a teacher teaching his/her students. 2. It's even impossible to explain to yourself when facing some middle-level/hard problems. Then I got another good idea: write everything down on papers. Finally, I found out that it was not that hard to solve these problems.
There are a lot of other learning strategies. In retrospect, I think it's lucky to be an engineer. Although it's hard, tough, brain-racking, I get to know a lot of learning strategies along the road. Sometimes you wonder if others are way smarter than you, but maybe they just know some learning strategies that you don't know, and they never give up.
After using Typora for a long time, I really don't think a separate preview is that necessary.