diff --git a/notebook/2021-07-22-14-01-10.org b/notebook/2021-07-22-14-01-10.org
index 26e80f4..d596d37 100644
--- a/notebook/2021-07-22-14-01-10.org
+++ b/notebook/2021-07-22-14-01-10.org
@@ -3,13 +3,13 @@
 :END:
 #+title: Communicate with others to learn
 #+date: 2021-07-22 14:01:10 +08:00
-#+date_modified: 2021-07-22 14:01:49 +08:00
+#+date_modified: 2021-07-30 13:45:22 +08:00
 #+language: en
 
 
-- easy to criticize others but not your own;
-  having others to look out for your work is a good incentive to get in touch
-- furthermore, depending on the community, you can learn more outside of the niche;
-  oftentimes, they also make off-topic discussions
-- though, you have to choose your community and target audience to make more effective feedback
-- [[roam:Niche projects brings more interesting audience]]
+Easy to criticize others but not your own.
+Having others to look out for your work is a good incentive to get in touch.
+Furthermore, depending on the community, you can learn more outside of the niche as oftentimes, they also make off-topic discussions.
+This is best used for making a quick feedback loop especially [[id:10214008-71da-4d1e-b761-80e671d6fc40][When starting out, focus on quantity over quality]].
+
+Though, you have to choose your community and target audience to make more effective feedback.
diff --git a/notebook/2021-07-30-13-34-59.org b/notebook/2021-07-30-13-34-59.org
new file mode 100644
index 0000000..b50da24
--- /dev/null
+++ b/notebook/2021-07-30-13-34-59.org
@@ -0,0 +1,12 @@
+:PROPERTIES:
+:ID:       864dfb57-af7c-4f03-80ea-fac2a0735b9e
+:END:
+#+title: Niche projects brings more interesting audience
+#+date: 2021-07-30 13:34:59 +08:00
+#+date_modified: 2021-07-30 13:45:18 +08:00
+#+language: en
+
+
+- most niche projects only cater to smaller audience
+- smaller audience means there is lower noise and the feedback often comes from people who are genuinely interested in your project
+- when done correctly, this is one of the more intimate examples of [[id:6f9c552f-055b-4238-874e-8608006ce0ca][Communicate with others to learn]]
diff --git a/notebook/2021-08-01-07-49-34.org b/notebook/2021-08-01-07-49-34.org
new file mode 100644
index 0000000..65f58e0
--- /dev/null
+++ b/notebook/2021-08-01-07-49-34.org
@@ -0,0 +1,18 @@
+:PROPERTIES:
+:ID:       3a605fb2-b867-41c2-bcf9-00ef772808e5
+:END:
+#+title: Show the result at the front
+#+date: 2021-08-01 07:49:34 +08:00
+#+date_modified: 2021-08-01 07:50:23 +08:00
+#+language: en
+
+
+- it makes for a quicker time evaluating whether this is something valuable for the audience
+- assume that most of the audience does not want to read since it isn't their job unless necessary
+- a disgruntled reader from the bad would make a worse impression than a reader that didn't find the thing valuable
+- most of the audience have a rough idea of what you're about to discuss;
+  remember the [[id:79357d56-74bf-4854-820c-c0ad849f2468][Classic prose]] model, they are interested in your solution or what you have done (i.e., workflow, solutions);
+  otherwise, they wouldn't consult to your piece in the first place
+- examples:
+  + abstracts in academic papers
+  + showcases in tutorials
diff --git a/notebook/2021-08-01-07-50-47.org b/notebook/2021-08-01-07-50-47.org
new file mode 100644
index 0000000..f03974f
--- /dev/null
+++ b/notebook/2021-08-01-07-50-47.org
@@ -0,0 +1,21 @@
+:PROPERTIES:
+:ID:       e5d4cb07-d0e6-4bda-b2fc-426240b04f78
+:END:
+#+title: Specific use cases are better than step-by-step tutorials
+#+date: 2021-08-01 07:50:47 +08:00
+#+date_modified: 2021-08-01 07:50:55 +08:00
+#+language: en
+
+
+- a written specific use case showcases multiple things;
+  a step-by-step tutorial mostly follow one with a fixed path
+- usually because it [[id:3a605fb2-b867-41c2-bcf9-00ef772808e5][Show the result at the front]];
+  similar reasons as to why [[id:e158b742-53c7-4442-9af3-489ea8240af9][Examples and stories are more memorable than explanations]]
+- examples:
+  + devlogs which a lot of the [[roam:Game development]] creates
+  + a lot of blog posts that tackles only one specific thing by its author usually to make them remember that thing
+- from a content creator perspective, it creates more interesting options (e.g., skits, persona) that are usually unneeded in a tutorial;
+  it can take advantage of our tendency to [[id:9a11ef31-b2a7-43a9-a7a9-48f191838c6e][Prefer referencing over remembering]] by being more memorable
+- with it, we can [[id:0dbfee88-cdce-48d1-9a10-23fc12d9bcd5][Refer to advanced resources when skill-building for a solid short-term goal]]
+- this is not a false dichotomy, overall;
+  a tutorial can make for a interesting piece if it's leaning more on specific use cases