Engineering Notes

This repository is my Obsidian vault for engineering notes: DSA, algorithms, system design, books, and technologies like Redis, Postgres, Kafka, Kubernetes, and AWS.

Preptin feeds coding submissions into dsa-algo-practice/. Treat that folder as the raw practice feed, then build curated notes around it in DSA/, Algorithms/, and the topic folders.

Start Here

• Open [[Indexes/Home]] as the vault home note.
• Drop rough notes into [[00 Inbox/Index]] and sort them later.
• Use [[Indexes/DSA Practice]] to browse the Preptin-generated submission feed.
• Use templates from [[Templates/Index]] when creating new problem, concept, system design, technology, or book notes.

Vault Map

• [[DSA/Index]] - data structures, concepts, practice review notes, and cheatsheets.
• [[Algorithms/Index]] - algorithm families and implementation notes.
• [[System Design/Index]] - concepts, case studies, patterns, and tradeoffs.
• [[Staff Engineering/Index]] - senior/staff execution, strategy, influence, and interview prep.
• [[Technologies/Index]] - practical notes for Redis, Postgres, Kafka, Kubernetes, AWS, and other tools.
• [[Books/Index]] - reading notes, summaries, quotes, and applied takeaways.
• [[References/Index]] - chapter/topic reading maps for filling the skeleton notes.
• [[dsa-algo-practice/README]] - generated practice submissions from Preptin.

Workflow

1. Capture: Put quick thoughts, links, and scratch notes in 00 Inbox/.
2. Practice: Let Preptin sync submissions into dsa-algo-practice/.
3. Curate: For every important solved problem, add the durable idea to DSA/, DSA/Concepts/, or Algorithms/ and link back to the raw submission.
4. Generalize: Move reusable ideas into DSA/Concepts/ or Algorithms/.
5. Review: Use index notes and tags to revisit weak areas.

Note Conventions

• Prefer one durable idea per note.
• Link aggressively using Obsidian wiki links.
• Keep generated submission files in dsa-algo-practice/ separate from curated explanations.
• Use tags like #dsa, #algo, #system-design, #staff, #technology, #book, #review, and #todo.
• For problem notes, include the platform, difficulty, pattern, approach, complexity, and link to the source solution.