interoperable components are efficient


Because interoperabile components are self-contained, they can be reused in different situations and are easily maintainable (changing one, updates all).

Related: notes/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

atomic things are self-containedatomic components are specific in content and self-contained. Having these attributes makes it interoperable.connecting ideas is powerful* encourages you to revisit old ideas and improves learning. * helps you discover new ideas through connections. * allows you to reuse your ideas in a different context. Related: notes/the brain is a network of ideasreuse 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 componentstwo principles of zettelkastenPrinciple of Atomicity**: Limit notes to a single topic for interoperability * See How to create useful links Principle of Connectivity**: Connect information together https://zettelkasten.de/posts/overview/#principlesHow to Create Useful Links with ZettelkastenThe linking feature of Zettelkasten is one of its most defining features, yet, it's the least understood. Linking ideas should be natural for us, but a lifetime of organization with the tree structure has made it difficult to adopt this new form of organization. To make links useful, we'll need to unlearn our old habits. This is an entire paradigm shift, so don't expect it to be easy. Don't group things, connect them The biggest mistake—and one I've made myself—is linking with categories. In oHow to take Fleeting 'programming' Notes in ObsidianWhile programming, I often spend a lot of time searching for things that I already know. Which is why taking programming notes can be so useful. It creates a personalized "cache" of notes. But how do I create meaningful programming notes that I can always go back to? Well stay here to find out! To create programming notes, I always start off with a title. I typically start with "how to" and end with "in {insert relevant language / framework}". This title succinctly explains the solution to the Confused On How To Manage Your Notes? Try This Simple Workflow.If you ever took notes on an article, video, or podcast and had no idea do with it, you're in the right place. Many existing solutions suggest adding tags, and creating many layers of nested folders. But oftentimes we find ourselves with folders with too many files or tags with too few members. The fault isn't in the person but in the note-taking system itself. My goal is to create a simple workflow where the content of the note organizes the note. This effectively eliminates the third step wheThe simplest way to use Zettelkasten for note managementEverywhere I look, I find complicated Zettelkasten workflows that require a multi-step setup process. On top of the setup, notes must be regularly reviewed and categorized. For some, this workflow may be a godsend, but for most, it's overkill. I'm here to unveil my method of using Zettelkasten. It may be unconventional, so beware. Zettelkasten Concepts Zettelkasten can be distilled into two principles: take atomic notes and make connections. What this means is to take notes that are limited toThe New Way To Write Connected and Personalized BlogsSo originally my blog was hosted on https://thinkwong.com. It used WordPress which was good for typical blogging, but I wanted more than that. I wanted to demonstrate the effectiveness of connected notes and the best way to do that was to lead by example. Hence, I created a website with Jekyll using a digital garden template. And because interoperable components are efficient I write less while providing more value. Since content is condensed into atomic bits, I can create highly personalized bI believe Zettelkasten is the future of note organizationThe number one goal with note organization is to make it easy to find notes when we need them. That being said, we often don't know when or what note we need. It's the reason full-text search isn't the single solution to note organization. The problem with grouping That's where folder and tags come into play. We use folders and tags to group similar notes together, but it becomes problematic once we accumulate hundreds of notes. As more notes are taken, more folders/tags are needed. Otherwise,Zettelkasten shouldn't be complicated, but it is.Zettelkasten is Complicated There are a lot of things I like about Zettelkasten, but one thing I don't like is how complicated it is to set up. According to the building blocks of Zettelkasten blog post, a typical Zettelkasten system consists of an inbox, an archive, and a reference database. Inbox**: the gateway into your knowledge system (e.g. Google Notes, Email, Apple Notes, etc.) Archive**: the one, trusted place to look for information (e.g. Obsidian, Roam Research, etc.) Reference Data