Using Obsidian as an engineering knowledge base — my setup after 18 months
by Izudin Rashdan·May 22, 2026
Started using Obsidian for personal notes and it's evolved into something more structured. Sharing what works.
Folder structure I landed on:
- /Daily — one note per working day with tasks, meeting notes, decisions
- /Projects — one folder per active project with architecture notes, decisions, and open questions
- /Reference — stable reference material (API docs summaries, architecture diagrams as images, runbooks)
- /Snippets — code snippets I use regularly
Plugins that earn their place:
- Dataview: query your notes like a database. Shows me all open tasks across all projects
- Calendar: visual daily note navigation
- Templater: auto-fills templates with date, project name, etc.
What I don't do: Elaborate graph views, complex link taxonomies, Zettelkasten implementations. The simple folder structure works better for engineering notes than highly-linked knowledge graphs.