ybbond

My site. The main domain
Log | Files | Refs | README | LICENSE | CC-LICENSE

commit dd6aafaacbc8f96afb8b5d8e225afce07d2f0c1d
parent 420565db44716ce2595f453e387919caea854fd8
Author: Yohanes Bandung <bandungpenting@gmail.com>
Date:   Sat,  2 May 2020 19:47:12 +0700

content: fixes grammatical error and a lil enhancement
Diffstat:
Mcontent/posts/In Search of Good Writing App - Part 2, iA Writer vs iVim/index.md | 8++++----
Mcontent/posts/Trying bs-json and bs-fetch to Publish My Gist as Blog.md | 9+++++++--

2 files changed, 11 insertions(+), 6 deletions(-)

diff --git a/content/posts/In Search of Good Writing App - Part 2, iA Writer vs iVim/index.md b/content/posts/In Search of Good Writing App - Part 2, iA Writer vs iVim/index.md
@@ -18,7 +18,7 @@ Part 2 of my previous post: [In Search of Good Writing App - Bear vs Ulysses](/p
 
 ---
 
-In the previous post, I compared [Ulysses](https://ulysses.app/) and [Bear](https://bear.app). I ended up subscribing to Bear. Bear itself is a good writing app, with nice clean interface design, great synchronization between MacOS and iOS (or iPadOS) platform, with a _just right_ MarkDown implementation.
+In the previous post, I compared [Ulysses](https://ulysses.app/) and [Bear](https://bear.app). I ended up subscribing to Bear. Bear itself is a good writing app, with nice clean interface design, great synchronization between MacOS and iOS (or iPadOS) platform, and _just right_ MarkDown implementation.
 
 I feel satisfied with my three days of Bear usage. The subscription model does not bother me, but I found several aspect to reconsider:
 
@@ -26,7 +26,7 @@ I feel satisfied with my three days of Bear usage. The subscription model does n
 One thing I like from Ulysses is file versioning similar to MacOS's _Time Machine_. Bear lacks that feature, changes I made will replace the previous version of the file in iCloud. The only way to access file history in Bear is through undo. Yep, plain old undo.
 
 ### File Storage
-Bear store my notes in its own enclosed library. I have no option to store my notes in external folder. This issue makes me think about the continuity of this subscription. Other writer also stated [this issue](https://joseperez.fm/2019/goodbye-bear-hello-ia-writer/), and his post gave me the idea to check **iA Writer**.
+Bear stores my notes in its own enclosed library. I have no option to store my notes in external folder. This issue makes me think about the continuity of this subscription. Other writer also stated [this issue](https://joseperez.fm/2019/goodbye-bear-hello-ia-writer/), and his post gave me the idea to check **iA Writer**.
 
 ### Modal Editing
 I came from modal editing world. The lack of **Vim** keybinding annoys me. This aspect is of my very own opinion.
@@ -35,7 +35,7 @@ Thus came other candidates
 
 ## iA Writer
 
-I installed the trial version on Mac. The main takeaway is iA Writer give the writer full control of its edited file. It uses iCloud to sync between devices. Mac version also has file versioning similar to _Time Machine_. iA Writer also supports opening external folder, enabling me to edit markdown file from my GitHub Gist.
+I installed the trial version on Mac. The main takeaway is iA Writer gives the writer full control of its edited file. It uses iCloud to sync between devices. Mac version also has file versioning similar to _Time Machine_. iA Writer also supports opening external folder, enabling me to edit markdown file from my GitHub Gist.
 
 ![I tried iA Writer trial on Mac, with its syntax highlighting on](ia-writer-headline.png)
 
@@ -54,7 +54,7 @@ That is Goyo plugin on Vim. Then I searched for Vim in iPadOS. I found it.
 
 I thought Vim app in iOS will be limiting and can only edit the files in the app's bundle file. I found iVim can edit file from other source. It also supports vimrc and plugins too! [This posts](https://www.reddit.com/r/vim/comments/9ki5g8/ivim_ios_howtos/) helps me a lot.
 
-I configured my iVim as a Zen Writing Tool_. I installed `Goyo`, `vim-markdown`, and Tim Pope's essential shortcut plugins that have been accompanying my typing journey for 2 years. The result is satisfying:
+I configured my iVim as a _Zen Writing Tool_. I installed `Goyo`, `vim-markdown`, and Tim Pope's essential shortcut plugins that have been accompanying my typing journey for 2 years. The result is satisfying:
 
 I use all of Bear, iA Writer (on Mac) and iVim for a while, eliminated Bear because of its low I mentioned above, and feel that the lack of preview makes iVim lacky. I read from reddit and other "this app vs. that app" posts that iA Writer for iOS is a worth buy. I decided to try purchasing iA Writer for iOS. 
 
diff --git a/content/posts/Trying bs-json and bs-fetch to Publish My Gist as Blog.md b/content/posts/Trying bs-json and bs-fetch to Publish My Gist as Blog.md
@@ -7,13 +7,14 @@ tags:
 date: 2020-03-03T01:47:12
 ---
 
-#### disclaimer: this is not a tutorial
+**disclaimer: this is not a tutorial**
 
 I read an interesting article (from a website that features a great function to see its articles' revisions) about using GitHub Gist as a Blogging CMS. Here is [the post](https://bit.ly/2UForoW).
 
 Back then, my website was written in ReasonReact, and back then, I thought that implementing my own blog by fetching my Gist is a nice way to learn `bs-fetch` and `bs-json`.
 
 > tldr; the result can be seen here [reason.ybbond.dev/blog](https://reason.ybbond.dev/blog)
+
 ## Fun Moment
 Implementing `bs-fetch` was the easier of both, because I follow the example of HackerNews built with ReasonReact.
 
@@ -23,7 +24,7 @@ So, here the story goes...
 
 When I first writing the code for parsing the return JSON value to valid ReasonML record, I was in a bit of a hurry. I wrote the kickstarting code in a cafe while my friend is ordering something. I encountered an error that I fixed easily. What a pity that I forgot what that error was. More of a pity is if I remember I encountered that error, I will not stuck for so long.
 
-GitHub Gist endpoint gives verbose information about the gists, one of them is the type of the file. The return value store the file type as a value with object key `type`. ReasonML doesn't want its record key as string `type`, because it is a reserved keyword. So I made the key as `type_`. Error gone.
+GitHub Gist endpoint gives verbose information about the gists, one of them is the type of the file's programming language. The return value store the file type as a value with object key `type`. ReasonML doesn't want its record key as string `type`, because it is a reserved keyword. So I made the key as `type_`. Error gone.
 
 Then I stopped writing code for that time, and I forget the progress that I've made.
 
@@ -31,8 +32,12 @@ Not so long, I return to continue the progress. After coding for several LoCs an
 
 I try to log the parsed value part-by-part, try to reread the code up-and-down, but cannot find the culprit of the bug.
 
+## Solution!
+
 After 3 months or so, I tried to rewrite the code, side-by-side. The old code on the left, the new code on the right, and when I reached to the position of `type_` key, I realized that I am a stupid.
 
+The record value expects `type_` key, while I forgot to parse the Gist's return value as `type_`. 😿	
+
 Okay, I got bored writing this. Straight to the **conclusion** then!!
 
 ## Conclusion