Back to Forum

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.

#Obsidian#notes#knowledge-management#engineering
278 upvotes6 comments

Comments (6)

Nurul Syahirah22

The toxic positivity in some companies — "we're a family", "good vibes only" — is actually harmful to people dealing with real mental health challenges.

Damien Koh17

Psychological safety means being able to say "I'm struggling and I need support" without career consequences. How many Malaysian workplaces actually have that?

Shahida Husin13

My company added mental health to the employee survey and the results led to real policy changes. Anonymous data is powerful when leadership acts on it.