Mark's MarkDown
  • notes
    • elevator pitch
    • cs
      • languages
        • elixir
          • data pipelines
            • broadway kafka
            • broadway
          • features
            • tree of contents
          • tips
            • enum
            • elixir tips
        • git
          • git notes

Tree of Contents

  • notes
    • elevator pitch
    • cs
      • languages
        • elixir
          • data pipelines
            • broadway kafka
            • broadway
          • features
            • tree of contents
          • tips
            • enum
            • elixir tips
        • git
          • git notes
Source
Résumé

Home

2022-05-16
Another Tech Blog? ...Not Quite
[all notes]
Since the release of livebook.dev, I have been progressively moving my notes here. Recently, livebook.dev released the sections button which is making me rethink how I organize my notes.

The Quest for A Second Brain

If you’re like me, one of your most sinister yet silent adversaries is, …future self. Albeit pleasurable, spending a significant amount of time to level-up software engineering skills comes at a heavy cost - time. I’ve always struggled to centralize my software related notes in order to rinse and repeat a particular concept.

Like most of us, I desire to build a second brain with excellent back-linking capabilities. I love tools like Obsidian and have recently discovered Mem.ai, however, these type of note taking apps either feel more like personal tools or lack the organizational &/or presentational features that I’m looking for. Even with plugins, feature gaps with these tools currently keep my software notes a bit too localized. This static site, with livebook counterparts, is intended to materialize and prime my collection of learned insights for rapid fire recollection by future self.

DISCLAIMER - Feel free to use or copy at will. However, I do not claim any responsibility regarding the completeness of the examples contained as this app’s purpose is solely for self learning. Often, you will see impartial explanations because the example has been cherry-picked to note an area or concept that requires highlighting. Use the code at your own risk; always test and check what you copy. Thanks!