Dev shares docs-as-memory playbook: dynamic retrieval over summaries, standard frameworks, one source of truth
menhguin · x · 2026-11-07
A developer shares practical notes on keeping docs up to date for AI workflows: retrieve dynamically instead of summarizing (or at least timestamp summaries), enforce standard industry frameworks (FHIR for health, CFP for finance, design docs for code) to prevent loose conflicting files, link to direct logs/GitHub sources, and document each thing in at most one place to avoid staleness. Their coding prompts are now mostly documentation specs—"here are frontier lab blog posts, find something to apply." Quoted context: someone had Opus write a wiki-style memory system in an Obsidian vault and reports an unreasonably large uplift, calling it "RSI in one vault."
More from coding & agent
- Simon Willison: November 2025 was the inflection point for AI coding, mid-career engineers most at risk — 2C_ornot2C · 2026-11-08
- YC-backed boat.dev hits $1M ARR in 22 months after 6 pivots — zack_overflow · 2026-11-08
- Apple ships official Xcode plugin for Claude Code to build and debug iPhone apps — SumitGup · 2026-11-08
- Warp insider: coding agents are commoditized, the real fight is scaling agent factories — vikvang1 · 2026-11-08
- Creator shares a 4-seat AI content pipeline: AI researches, human keeps the voice — PrajwalTomar_ · 2026-11-08
- Researcher: Opus 5.5 ran pretraining scaling experiments unattended for a day — RylanSchaeffer · 2026-11-08