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]].
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.
- 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 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.