Code snippets, technical notes, and architecture decisions
Developers use Memos to save code snippets, debug notes, architecture decisions, and learning resources as short memos. Fenced code blocks, tags, and search make them easy to find again.
Home
Today
TIL: find the commit that introduced a string. #dev/til
git log -S "parseConfig" --oneline
đź’ˇ2
Yesterday
Why sessions moved to Redis
Decision: store sessions in Redis, not Postgres.
Because: login spikes locked the sessions table.
Revisit if we drop the cache tier. #dev/adr
2 days ago
Staging keeps timing out on the payments webhook #dev/debug
Completed: Check the retry headers
To do: Raise the proxy timeout to 30s
Example memos. Yours start private.
In practice
Ways it fits the day.
These are independent starting points, not a prescribed process. Keep only the parts that match your work.
Store reusable code snippets and command-line recipes
Document bug investigations and troubleshooting steps
Record architecture decisions and technical trade-offs
Collect learning resources while exploring new technologies
Track API endpoints, environment details, and configuration notes
Maintain personal development logs and TIL (Today I Learned) entries
Why Memos
The fit stays simple.
Syntax highlighting for common languages in fenced code blocks
Cmd/Ctrl+Enter saves a memo without leaving the keyboard
REST and gRPC APIs, webhooks, and a built-in MCP server connect Memos to your tools
Self-hosting keeps work notes on a server you run, and new memos start private
No titles to invent: write the snippet and add a #tag