Knowledge Log::Meta

This falls under RW section of Knowledge Log 2.5, where I read anything from any website such as Wikipedia, or even randomly read any research papers from arxiv.org. Here I'd like to discuss about how the rough SOP of this subdivision would be and hopefully I'd follow it in the coming future:

  1. Take a reading source
  2. Break it into contents
  3. Make a short summary of all sections

Optionally, create an infographics/chart/mindmaps for better understanding of certain topics.

The goals

  1. understand topics being read; technically or non-technical
  2. be a layman as much as possible to achieve point #1

Phases

  1. Idea formulation -> Gnotes/Keep/Topic Ideas
  2. First draft -> Topic Ideas
  3. Second draft -> Issues
  4. Third draft -> Repo code
  5. ???
  6. Publish -> Blog

Rules on writing summarized contents

This can be done in a lot of ways, though I can't really say I would only follow one rule at all times. However, the most important thing to get an article done is to make it as layman as I can possibly understand in the future.

Helpful resource on writing good layman summary. Also, take a look at these two types of papers: Narrative and descriptive.

To write a narrative essay, you’ll need to tell a story (usually about something that happened to you) in such a way that he audience learns a lesson or gains insight.

To write a descriptive essay, you’ll need to describe a person, object, or event so vividly that the reader feels like he/she could reach out and touch it.

As for my practice of writing, specifically, I usually write my own thoughts right after paraphrasing/translating a sentence. For instance, [paraphrased text] would be followed by my own words/thoughts on it. Only certain parts applied. It can be satirical and analogical in a way that I would understand it straight away, because I knew had written in a time-specific thought.

Technique on summarizing contents

  1. Read a part of an article
  2. Reread the part
  3. Divide into sections - understand important parts
  4. Write one-sentence summary of each section

Protip:

  • Paraphrase where needed - express with your own word
  • Avoid unnecessary wordings and repetitions
  • Avoid personal ideas and inferences
  • Use transition signals and conjunctions to combine ideas. wherever possible

Source

Content discovery

I did all of my research by an intensive Googling. However, I avoid taking notes from sources that are somewhat vague to my liking, for example newspaper articles which can be fabricated as the author is also summarizing the original source (s)he got from. I'd prefer taking from the original source (ie. blog posts, research papers etc). Although it could be too high-level technicality for my level of understanding.

Content writing style

A default template for writing style would be the 5W1H questions, or FAQ-based article.

(Experimental) Research writing style

Taken from Craig Wright's Satoshi and Science blog post:

Step 1: Question. The “thing” that you want to know.
Step 2: Research. Conduct research.
Step 3: Hypothesis. Educated guess or prediction of the outcome experiment.
Step 4: Experiment. Test the hypothesis.
Step 5: Observations. Data you collect during the experiment.
Step 6: Results/Conclusion.
Step 7: Communicate.

Source

Drafting

Drafting is mostly done in this repo's issue page. Some of my drafts are in my Gnotes notebook (private). But I'm slowly moving everything to this repo.

The content of this repo is where my final phase of draft writing be uploaded before publishing.

Topic Ideas page is mainly for a very rough draft.

Staying focus

Few ways I gather my contents for my blog:

  • Watching highly technical Youtube videos
  • Reading an enormous deep technical articles from the internet

However, watching and reading highly technical stuff from the internet doesn't make me to stay in focus, it always make me yawn sleepy. There are ways to fix this:

  • For videos: force myself to watch. Scribble notes from it; would lead to sparking my curiosity and stay awake.
  • For articles: use Firefox Pocket read aloud feature.

Other than that, I use Pomodoro technique in order to stay focus. Also, I installed Block Site addon for Firefox that helps me block some sites after certain period of time. Besides that, I also turned off my phone and put it far away from me. It really helps on eliminating distractions. #millenialproblems

Language used

Reason why I don't write in English is because I'm not well-versed in the language yet 😅

Writing tools

So far, I've been using Google Translate heavily to translate any term from English to Malay. I have the English word in mind, but sometimes I would need its help to translate it to Malay. It helps a lot!

Also, some of the writing routine I did was going to Google and search for definition of a word -- eg. "define [keyword]". Or finding similar word (synonyms) for paraphrasing texts.

Audience

I recently wrote a post about buying bitcoin on Luno Exchange. I noticed that my original agenda has faded since the traffic from the said post alone has made me think about what to write next for my audience.

Readers are my secondary motivation in writing, because when writing, I don't want to always think about who are going to read my post. I'd like to keep my main motivation to write as what I have described above, to learn something and anything without caring so much about people's expectation.

Unpopular opinions

  • Listening to piano solo music while writing helps (sasau music also helps)
  • Night time after 12 am is the best time to write. Nocturnal friends, put your hands up...?

Further readings

  1. How to Write a Technical Paper

Learning Resources

  1. Arxiv
  2. Papers We Love
  3. Google Scholar
  4. Sci-Hub
  5. Library Genesis
  6. Academic Torrents
  7. BookZZ - Guides to Bookzz here
  8. Project Gutenberg - literature ebook downloads
  9. Free programming books
  10. Aerospace Research Central
  11. Academia.edu

Courtesy of Papers We Love: