Capture it while it's fresh
Write a few lines or record a voice memo after the meeting, the incident, the launch. The raw entry is kept exactly as you said it, and audio is never stored.


a notebook for software engineers
Decisions, incidents, trade-offs, the things you shipped and what you learned from them. Captured as they happen and kept as a memory you can draw on for interviews, reviews and reflection.


One entrybecomes a few structured experiences, not a pile of notes.
Every answercites the experiences it was built from.
No audiois kept after transcription, in the browser or on the server.
Write a few lines or record a voice memo after the meeting, the incident, the launch. The raw entry is kept exactly as you said it, and audio is never stored.


Suggested experiences come back structured: the problem, what you decided, the alternatives, the result. Nothing counts until you confirm it, and your edits are never overwritten.


Before an interview or a review, ask a question and get a short answer built only from what you confirmed, with numbered sources you can open.


Have three real stories ready for “tell me about a time you…” instead of the one you remember under pressure.
Write your self review from a year of evidence, not the last two weeks.
Show scope and impact with dates, projects and results your manager can check.
Bring the decision you made last month and what came of it.
AI drafts stay drafts. Refinements only fill empty fields, and confirmed memories get proposals, never silent edits.
Answers cite the experiences they come from. When nothing fits, it says so instead of stretching.
Recordings are transcribed and discarded. You always review the transcript before it becomes an entry.
Removing a memory also removes what was derived from it, including past answers that quoted it.
Future you will thank you for it, in the next interview and the next review.
Sign in