# Note-Taking with Obsidian Jan 5, 2025 #humans #note-taking The mind is a chaotic vortex of ideas, insights, and half-formed connections. This cognitive chaos isn't just distracting - it's actively holding us back from reaching our full creative and intellectual potential. ![[2fe35bbad83bb455c0c77734d39493a96d9307b611837c15743863ac3130d3b0b5a93deacc17404fa278b3a9887f8bf45ba501fe4bc24cbe154ef5e3a96c61cf.png]] ## The Problem with Mental Clutter Our brains excel at generating ideas but are surprisingly terrible at retrieving and organising them. The fundamental principle of the organised mind is offloading this cognitive burden onto external systems. Without a reliable system, we're left with: - Distorted memories and fragmented insights - Decision fatigue from constant mental juggling - Inability to see valuable connections between ideas ## From Chaos to Clarity The solution isn't fighting against our mind's natural tendency toward chaos - it's embracing tools that work with our cognitive architecture. Active thinking through embodied cognition (like walking or drawing) helps process complex thoughts. But for true clarity, we need a robust external system. This is where I found Obsidian to be the most helpful, it shines as a second brain. Unlike rigid note-taking apps, the bidirectional linking mirrors how our minds naturally connect ideas. The Zettelkasten and PARA methods provide flexible frameworks that eliminate the cognitive overhead of deciding where to store information. For example, while studying `[[Transformers]]`, I might note that attention mechanisms are crucial for handling sequential data. This naturally links to my notes on `[[Self Attention]]`, which in turn connects to both `[[Query-Key-Value Operations]]` and `[[Positional Encoding]]`. When reviewing `[[BERT]]`, I can see it builds on these transformer concepts while adding `[[Masked Language Modeling]]`. These connections become even more valuable when exploring modern architectures. A note on `[[Vision Transformers]]` might reference back to `[[CNN vs Attention]]` and `[[Patch Embeddings]]`, while also linking forward to applications in `[[Foundation Models]]`. Each link represents a potential exploration path, allowing ideas to flow naturally between concepts. The beauty is in discovering unexpected connections. While writing about `[[Gradient Descent]]`, I might link to both `[[Optimization Algorithms]]` and `[[Loss Landscapes]]`, which could unexpectedly connect to my notes on `[[Neural Network Architecture Search]]` through shared concepts about optimisation in high-dimensional spaces. ## Beyond Basic Note-Taking The real power comes from treating your notes as a living knowledge graph rather than a static repository. Through features like backlinks and MOCs (Maps of Content), seemingly disparate ideas can form unexpected connections. This emergent structure allows your external thinking system to become more valuable than the sum of its individual notes. The goal isn't perfect organisation. It's about reducing friction between having an insight and being able to build upon it later. ## My Zettelkasten Setup I keep my vault structure deliberately minimal to reduce decision fatigue. ### Root Directory Keep this clean - only folders, no loose notes. ### Notes Directory My permanent notes live here. These are refined, crystallized thoughts that form my core knowledge base. Characteristics: - Atomic: one idea per note - Heavily linked to other notes - Written in my own words - Timeless rather than temporal - Formatted for future-me ### Daily Notes My inbox and processing area. Daily notes capture the stream of consciousness and serve as entry points into the system. Key features: - Meeting notes - Random insights - Task tracking ### Fleeting Notes Think of these as cognitive scratch paper - quick, messy, and temporary. Purpose: - Raw thoughts - Quick captures - Ideas to process later - Draft content - Should be processed within 24-48 hours - Delete after processing into permanent notes ### Literature Notes My external knowledge repository. These notes represent my interaction with content I consume. Contents: - Blog post summaries - Book notes - Paper annotations - Video notes - Podcast highlights - Course notes ### Attachments The asset library. Contains: - Images - PDFs - Canvases - Screenshots - Downloaded resources - Reference materials The key is to maintaining clear boundaries between these spaces while allow ideas to flow freely between them. Think of it as cognitive spaces with different levels of refinement and permanence. ## Speed Over Perfection The key to maintaining momentum is reducing friction. Quick capture is essential - notes should take seconds to create. I use templates aggressively to maintain consistency without sacrificing speed. **Core Templates** For permanent notes: ```plaintext --- created: {{date}} type: zettel aliases: tags: status: draft/refined/published references: links: --- # Main Idea ## Context ## Key Points ## Related Concepts ``` For literature notes: ```plaintext --- created: {{date}} type: literature source: author: completed: --- # Summary ## Key Takeaways ## Quotes ## Questions & Thoughts ``` For daily notes: ```plaintext --- created: {{date}} type: daily --- ## Tasks - [ ] Process fleeting notes - [ ] Review literature notes ## Notes & Ideas ## Meeting Notes ## Content Consumed ``` **Template Hotkeys**: - Ctrl+J: Zettel template/Literature template/Daily template The real productivity gain comes from muscle memory. After a week of using these templates, you'll create structured notes without thinking. The frontmatter metadata becomes invaluable for searching and organising later. **Pro Tips**: - Use status tags to track note maturity - Keep templates minimal at first - Add custom fields as patterns emerge - Use consistent formatting - Include prompts for important sections Templates should reduce cognitive load, not add to it. Start simple and evolve them based on your actual usage patterns. ## Core Principles **Atomic Notes**: Each note contains exactly one idea. This creates clean interfaces between concepts that can be recombined later. Think of it like functional programming - each note should have a single responsibility and clear inputs/outputs. For example: - A note on `[[Backpropagation]]` should focus solely on that algorithm - Related concepts like `[[Chain Rule]]` and `[[Automatic Differentiation]]` get their own notes - Complex topics like `[[Transformer Architecture]]` should be split into atomic components **Natural Emergence**: Let structure emerge organically rather than forcing hierarchy. The system should feel like an extension of your thinking, not a straitjacket. This means: - Start with rough notes and refine over time - Create links as you naturally see connections - Let MOCs (Maps of Content) form around clusters of related notes - Don't force notes into predetermined categories - Use tags sparingly and let them emerge from patterns **Active Linking**: The real magic happens through connections. Every note should link to at least one other note to avoid orphaned ideas. Practice: - Forward linking: Connect to existing notes - Backward linking: Review backlinks to find patterns - Predictive linking: Create links to notes you know you'll write **Progressive Summarization**: Layer your notes like an onion: - Layer 1: Raw capture - Layer 2: Bold important points - Layer 3: Highlight crucial insights - Layer 4: Mini-summary at top - Layer 5: Permanent note synthesis **Evergreen Notes**: Treat notes as living documents: - Regularly revisit and refine - Update with new insights - Merge related notes - Split notes that become too complex - Maintain version history through git The goal is building a system that thinks with you, not for you. Your notes should act as conversation partners suggesting connections and surfacing insights you might have missed. The best insights often come from unexpected connections between seemingly unrelated notes. The more atomic and well-linked your notes, the more emergent properties your system will develop. ## Power Features **Quick Capture**: Use Cmd/Ctrl+O to search existing notes before creating new ones. This prevents duplicate notes and encourages connection-making. Power moves include: - Cmd+O for quick switching between notes - Cmd+P for command palette access - Cmd+Shift+F for global search - Alt+Click to open notes in new pane - Cmd+Click on links to open in new tab **Properties**: Add metadata to notes for better organisation and retrieval. Properties act like spreadsheet columns for your notes: ```plaintext --- status: evergreen difficulty: intermediate last_reviewed: 2024-01-05 related_topics: - neural_networks - optimization confidence: high --- ``` These properties enable: - Custom filters and views - Dynamic table generation - Automated note maintenance - Spaced repetition tracking - Knowledge maturity tracking **Visual Hierarchy**: For notes you want to polish: _Callouts for Different Purposes_: ```plaintext > [!INFO] Key Concept > Core ideas that need emphasis > [!WARNING] Common Pitfalls > Things to watch out for > [!TIP] Pro Move > Advanced techniques > [!NOTE] Further Reading > Related resources ``` _Typography and Structure_: - Use H1 (#) for note titles only - H2 (##) for major sections - H3 (###) for subsections - Bold for key terms - _Italics_ for emphasis - `code blocks` for technical details _Advanced Formatting_: ```plaintext ==highlighted text== for crucial points ~~strikethrough~~ for outdated info - [ ] checkboxes for actionable items - [x] completed items ``` _Tables for Structured Data_: ```plaintext | Concept | Use Case | Example | |---------|----------|---------| | Embedding | Text representation | Word2Vec | | Attention | Sequential data | Transformers | ``` These features should reduce friction, not create it. Only use what serves your thinking process - everything else is cognitive overhead. ## Essential Plugins **Copy Document as HTML**: A lifesaver for knowledge sharing. Instantly converts your markdown masterpieces into properly formatted HTML, preserving styling and structure. Perfect for: - Publishing notes to blogs - Sharing with non-Obsidian users - Maintaining formatting consistency across platforms **Hash Pasted Image**: Eliminates the cognitive overhead of image management. Instead of breaking flow to name screenshots, it automatically: - Generates unique hash names for images - Moves them to your attachments folder - Maintains clean references - Prevents duplicate images **Zoottelkeeper**: The automated librarian for your digital brain. Creates and maintains Maps of Content (MOCs) without manual intervention: - Auto-generates folder overviews - Updates index files automatically - Creates navigable content structures - Reduces maintenance overhead ## Aesthetic Optimisation The interface where you spend hours thinking should be a joy to use. **Font Selection**: - Body: Lora for clean, readable text - Headers: Lora for clean, readable text - Monospace: IBM Plex Mono for a beautiful contrast - Line height: 1.6 for optimal readability - Font size: 16px base size with modular scale **Theme Customisation**: The Minimal theme provides the cleanest canvas for thought. Also enable: - Line numbers - Live Preview - Show inline title - Show indentation lines - Strict line breaks **Layout Tweaks**: - Hide unnecessary UI elements - Use custom snippets for personal touches Your note-taking environment should feel like a high-end IDE for thoughts. The goal is to make the interface disappear, leaving just you and your ideas. ## Building Your Knowledge Graph The goal isn't to create a perfect organisational system - it's to build a living, breathing knowledge network that grows with your understanding. Review and refine your notes regularly, but don't get caught up in organisation perfectionism. **Growth Patterns**: - Start with seed notes on core concepts - Create hub notes for major themes - Let connections emerge through daily use - Regularly review orphaned notes - Prune and merge redundant content **Knowledge Life cycle**: 1. Capture fleeting thoughts instantly 2. Process into permanent notes within 48 hours 3. Connect to existing knowledge 4. Review and refine periodically **Emergence Strategies**: - Use the graph view to identify clusters - Create MOCs for dense topic areas - Look for unexpected connections - Follow your curiosity > The best note-taking system is the one you'll actually use consistently. Keep it lightweight, make it visual, and let the connections emerge naturally. ## Final Thoughts A well-configured Obsidian setup removes friction from the thinking process. These plugins and customisation aren't just aesthetic choices - they're cognitive ergonomics that make maintaining your second brain effortless. **Key Takeaways**: - Start simple, grow organically - Focus on capturing ideas quickly - Let structure emerge from use - Review and refine regularly - Trust your future self **Next Steps**: 1. Set up your basic vault structure 2. Install core plugins 3. Create your essential templates 4. Start capturing daily notes 5. Build the habit of linking 6. Review weekly for patterns 7. Adjust based on what works Your knowledge graph is a garden, not a factory. It needs regular tending but shouldn't feel like work. The joy is in watching it grow and discovering new connections you never expected to find. The real power of this system emerges when you stop trying to control it and start letting it surprise you with insights. Your digital garden will become more valuable than you could have planned - precisely because you didn't plan it.