reusing components is more efficient

so we don't need to "reinvent the wheel"

related to reuse code for efficiency and maintainabilityreuse code for efficiency and maintainabilityIn coding, the goal is to notes/get things done mentality and the shortest path to this is by being efficient. One way to be efficient is to not reinvent the wheel and use interoperable components

Backlinks

notes are too big when info retrieval is slowBecause getting info is slow it's harder to follow principle of atomicity and reusing the component is hard notes/reusing components is more efficientLearn Zettelkasten by Example #3: New Note or NotIntro Blurb In this post, I write fleeting notes on an article titled "When Should You Start a New Note?". This article gives tips on when to create a note and when to use an existing note. Hopefully, this process can give you ideas about how to improve your Zettelkasten workflow My Notes Article Link: https://zettelkasten.de/posts/when-start-new-note/ * sometimes it's difficult to know whether to create a new note or append an existing note. And that can stop note-taking entirely because thSharing Connected Notes - Fleeting Notes x ObsidianConnected notes are powerful. They allow you to expand upon different ideas within its own context and make it easy reuse notes. There exists Obsidian publish but this service is gated by a paywall and is geared towards content creators. Sometimes we want to share a note (+ all the links within the note) without the hassle of setting up a website or paying a monthly fee. Some example use cases include: * explaining a concept to a friend * sharing notes for a particular class * showcasing the c