Update note-related notes

Specifically about consuming information and note-taking. It is just a
simple realization about those things. Quite simple but I think it is a
good important reminder for my future self here.

2020-07-06-03-47-52.org

@@ -1,6 +1,6 @@
 #+title: Refer to advanced resources when skill-building for a solid short-term goal
 #+date: "2020-07-06 03:47:52 +08:00"
-#+date_modified: "2020-09-09 05:09:40 +08:00"
+#+date_modified: "2021-04-30 14:23:28 +08:00"
 #+language: en
 
 
@@ -14,3 +14,6 @@ Other side effects include creating deliberate practice sessions and taking the
 
 Of course, this does not entirely replace looking out for beginner-friendly resources and communities as an entryway (see [[file:2020-07-01-23-19-07.org][Information literacy]]).
 On the other hand, this prevents you from quickly entering tutorial purgatory where you'll be stuck for an indefinite amount of time.
+
+Also this could lead into actively consuming just the resources without the practice.
+[[file:2021-04-30-14-12-52.org][Create roadmaps to stay on track]].

2020-07-08-22-42-47.org

@@ -1,29 +1,28 @@
 #+title: When learning a new skill, begin with a specific end-goal to create a solid starting point
 #+date: "2020-07-08 22:42:47 +08:00"
-#+date_modified: "2020-12-05 21:43:46 +08:00"
+#+date_modified: "2021-04-24 01:18:56 +08:00"
 #+language: en
 
 
 This top-bottom learning approach (i.e., specific to general topics) is often used by self-learners.
 It usually involves something like wanting to create a 2.5D fighting game rivalling [[https://en.wikipedia.org/wiki/Arc_System_Works][Arc System Works]], a gorgeous anime-inspired illustration, [[https://www.youtube.com/watch?v=TF9I1GxNdJQ][a flashy short animation]], or [[https://www.youtube.com/watch?v=ZwR0zFe57Y4][a cool-looking demoscene]].
 
-Most of the time, the process of skill acquisition happens similarly to the following workflow with varying effectiveness.
-(As obvious as it seems, simply laying it out can add some perspectives [at least to me].)
+Most of the time, the process of skill acquisition happens to the following workflow with some effectiveness.
 
 - Document your specific example (e.g., a website, a drawing, a 3D scene).
   You can [[file:2020-07-06-03-47-52.org][Refer to advanced resources when skill-building for a solid short-term goal]] to clear your specific example similar to a final proof-reading before you submit your paper.
+
 - Then, try to learn the specific example.
+
 - For every unknown part of the example, try to understand the underlying concepts.
   If the underlying concept is not yet understood, then dig deeper into understanding the underlying concept of that underlying concept ad infinitum.
+
 - With the tree of to-be-understood underlying concepts, take a peek between each underlying concepts  of various depths until you can easily see the connections between them.
+
 - Work your way up the knowledge tree you've just created until you can reproduce/create the example with your newfound hierarchical knowledge.
 
 The gist of the above list is to create your roadmap.
 That way, it doesn't lead you into aimlessly learning stuff and get you efficient in upping your skill level.
 
-The general idea is having a specific example aids you in creating an outline of the related general concepts which in turn aids you into learning what you want to learn.
-You can easily see what gaps of knowledge should you fill to fully understand a specific concept whether it is simple, technical, or complex.
-I recommend to record the outline in a plain-text [[file:2020-04-15-14-35-55.org][Note-taking]] tool like [[file:2020-04-20-16-51-40.org][Org-mode]], Asciidoctor, or Markdown.
-
 Not every attempts of skill acquisition is suitable with this workflow with some skills need more experiments than others.
 The above workflow is more suitable to acquire advanced skills than entry-level skills where aiming for a perfect first try is (obviously) not an attractive goal.

2021-04-07-18-53-58.org

@@ -1,6 +1,6 @@
 #+title: Future-proofing your notes is only worth if the future is relevant
 #+date: "2021-04-07 18:53:58 +08:00"
-#+date_modified: "2021-04-07 19:52:57 +08:00"
+#+date_modified: "2021-04-24 18:47:36 +08:00"
 #+language: en
 
 
@@ -13,3 +13,5 @@ You have to assign a garbage day at some point.
 Future-proofing your notes creates pressure on managing your note-taking seriously and efficiently.
 You don't want to take notes haphazardly and the overall notes structure will stay the same throughout a year.
 They should eventually evolve into [[file:2020-05-07-21-53-21.org][Evergreen notes]], branching out of the original notes structure and making a better graph for navigation.
+
+An alternative to trashing your notes could be creating a dedicated folder (see [[file:2020-06-25-12-37-23.org][Create a writing inbox to store your thoughts]]).

2021-04-26-18-59-30.org

@@ -0,0 +1,20 @@
+#+title: When note-taking, don't satisfy your ego
+#+date: "2021-04-26 18:59:30 +08:00"
+#+date_modified: "2021-04-26 19:00:33 +08:00"
+#+language: en
+
+
+Found some inconsistent titles?
+Improper metadata?
+Incorrect datetime format?
+Just correct them as you stumble upon them.
+
+A similar dilemma I have yesterday is trying to format the metadata my Org mode files and sorting them alphabetically.
+I've written a script and as I'm not experienced in text processing, I spent most of my time reading up documentation on the tools.
+I did learned something with the tools but I've realized it's a big waste of time especially if my notes have grown.
+If I found another hip and new note-taking method and it doesn't conform to the new ideal notes in my mind, then I should relax and try it out.
+If it's good and I integrated it, I'll simply link it to my old notes.
+
+My personal notes, no matter how poorly written or unmaintained, are still valuable.
+So if you have tendencies like this, just relax and correct them. :)
+Trashing notes should be taken as a last resort if you're sure it is not relevant to you in the present and in the near future (see [[file:2021-04-07-18-53-58.org][Future-proofing your notes is only worth if the future is relevant]]).

2021-04-30-14-12-52.org

@@ -0,0 +1,13 @@
+#+title: Create roadmaps to stay on track
+#+date: "2021-04-30 14:12:52 +08:00"
+#+date_modified: "2021-04-30 14:22:18 +08:00"
+#+language: en
+
+
+The internet is a place full of information.
+In fact, too full.
+
+You could consume endless information from one resource to another and create stagnation because you're adapting too many ideas at a time.
+[fn:: On the other hand, this sounds like the Collector's Fallacy.]
+Having a roadmap helps you to stay on track whether you're studying for a job, creating a new project, or learning a new hobby.
+This roadmap could be just a simple to-do list, an elaborate plan, or a one-line description of the output you expect [fn:: This is still a terrible example but it should eventually evolve into details.].