From r/ObsidianMD 📅 • 📊 18 upvotes • ⭐ 8/10 • 🚀 high
*Analysis generated: Mar 2, 2026*
🔗 Source: View on Reddit
—

Summary

The author is debating between a simple ‘note per person’ system with relationship details embedded within, versus a more structured approach creating dedicated notes for each relationship (e.g., ‘Person-A-Person-B-Friendship’). They’re concerned about note bloat with the latter approach but feel it’s more ‘DRY’ (Don’t Repeat Yourself) from a programming perspective.

Key Insights

1. The tension between simplicity and structured data in Obsidian.
2. The potential for note bloat when modeling relationships explicitly.
3. The value of ‘DRY’ principles in knowledge management.

Enhancement Suggestions

No enhancement suggestions available

Analysis

This post highlights a common Obsidian dilemma: balancing simplicity with structured data. The question of how to represent relationships is fundamental to building a useful knowledge graph. The author’s concern about note bloat is valid and a frequent issue for Obsidian users.
—
*Curated by AI for Paul’s Vault Members*