Home

TL;DR

• Configuration
• Work
  • Skills
  • Projects
• Life: free time wasting for a better life
  • Living (* required absolutely)
    • Health
    • Relationship: family and lovers.
    • Sex
  • Hobbies
    • Consuming
      • watching animes / manga
      • playing games
      • reading books / galgame
      • listening to musics / podcasts
    • Creation
      • Weekly
      • drawing pixel illustration

Welcome my second brain I tried to build with obsidian & quartz. I used logseq before and now I give it up, which is the reason why some part of notes is ugly and wired¹.

Anyway, wish you have a fun time. That would be my pleasure.

Why choose work & life classify?

The hard truth is, we’re spending the most time of life to work.² During this time, solving business problems is the main subject.

Persistent store

Considered working business, the part of working should not be open-source, they deserved a private repository.

Then you should take care avoiding the wrong second brain, because notes should not be your trash inbox, which always make your system growing up, with high entropy increases, until they being a black hole.

So dealing problem with project is the main subject for this notes, which should have a certain deadline.

PKM announcement: Soft rules

Whatever you’re using, the half life of something (such as rules) is not changed fast. I would try my best to build it to a evergreen tree. ³

IMPORTANT

Using syntax sugar as less as possible.

Such like macros / properties:: / org-mode / task management on logseq, wikitext / embed tweet/youtube as image on obsidian as well.

Page naming

• Use - to connect two word rather blank for readable url.
• Use plural of noun to separate different pages
  • using book to talk something topic.
  • using books/xxx to talk something specific.
• Don’t add the [[]] in page_name
• Never renaming page name after git commit.
  • the pain of renaming on git is high, which means the history would be lost at all.

Properties

Keep order, dictionary order is the best.

Template

• Every main topic page should have a template.
• All template properties should extend page.
  • Keep adding less properties as much as possible.

Tags

Using #[[]] instead of #. They would be popped menu friendly, while editing again.

Hierarchy

Hierarchy/Namespace is not silver bullet. Delay your use of namespaces until you have refined your understanding of how they might suit your workflows. ⁴

© Copyright

Copyright 2022 - 2024 bGZo. All rights reserved. The contents is licensed under a CC-BY-SA; the code is under MIT licence. The contents and comments are copyright their respective authors, submission implies license to publish on this web site.

Footnotes

1. : two formats would be existed on here: outliner & paragraph. ↩

2. If you are a student, or someone else, the work could be something you worked for living. Whether they should separate with space time, there are a thousand Hamlets in a thousand people’s eyes. At least in China, space time always conflicts with work, so talking about that is always ambiguous… ↩

3. Maybe the flow you have to change in next version, or the problem maybe solved, it’s really not have too much value. ↩

4. https://www.logseqmastery.com/blog/logseq-namespaces, https://discuss.logseq.com/t/outline-overview-for-sidebar/740/19 ↩