A private work memory for software engineers.
Remember what you shipped, explain your impact, and come back to explain your story.
Improve GitHub sync reliability by adding retry handling for failed background jobs
Added bounded retry handling with exponential backoff around the sync jobs, plus a dead-letter path so a job that exhausts its retries is recorded i…
Sync reliability is invisible when it works and damaging when it doesn’t. Missing activity quietly corrupts the record the whole product is built on…
How Engineer Journal connects to GitHub.
From GitHub to journal in four quick steps. GitHub authorization is what lets Engineer Journal read your activity. You choose which authorized repositories are summarized, and access stays read-only.
Create your Engineer Journal account with GitHub. No separate password to manage.
Grant read-only access so Engineer Journal can read the GitHub activity needed to create your summaries.
Pick the authorized repositories you want included in your journal. You can change the selection anytime.
Create a daily, weekly, PR, sprint, or performance-review summary and save it to your private journal.
See your work history take shape.
Engineer Journal turns GitHub activity into saved entries you can browse, search, and reuse later.
What you’ll find kept inside.
For individual engineers keeping their own record.
A page on what you shipped, decided, and learned — written for you from the day’s activity.
Zoom out to the arc of a week or the chapter of a sprint without rereading every PR.
Turn one pull request into a written record: what changed, why, and what it cost.
Compile saved summaries into paste-ready, edit-friendly review material.
Flag the work that mattered so the important entries surface when it counts.
Filter your whole record by repo, theme, and date — your work, kept and findable.
Review season shouldn’t start with six months of scrolling.
Most engineers forget their own work by the time reviews come around. Engineer Journal turns the PR summaries you already saved into review-ready notes.
- Saved summaries are reused. No re-analyzing the same PRs.
- Historical backfills can analyze missing PRs when you need them.
- Output is simple, paste-ready, and easy to edit before it ships.
Performance review — H1 2026
Led the live-shipments migration to server-sent events, cutting ~33% of read traffic on a core service.
Shipped the billing + usage-budget system end to end, from Stripe checkout to enforcement.
Hardened the GitHub App repo-access path and made multi-repo reviews reliable.
Honest about what we touch, and what we keep.
We send the GitHub activity you choose to include to Anthropic to generate your summaries, then store the summaries for your memory. Not your raw code or diffs. Your journal content isn’t used to train AI models.
- Read-only GitHub access. Never write.
- Only the repositories you choose.
- Access can be changed or revoked from GitHub at any time.
- Generated summaries and journal entries, so you can revisit and compile them.
- Your account, settings, and which repos you selected.
- Payments are handled by Stripe. We never see your card details.
A note from the founder.
I built Engineer Journal because I kept running into the same problem: I would do the work, merge the PRs, fix the bugs, make the decisions. Then weeks or months later I would struggle to explain what I had actually accomplished.
Performance reviews, weekly updates, interviews, and resumes all ask engineers to tell the story of their work. But most of that story is scattered across GitHub, tickets, notes, and memory.
Engineer Journal is my attempt to make that easier. It turns the work you already did into a private journal you can come back to when you need to remember it, explain it, or reuse it.
Priced in summaries, not seats.
See how the app works.
Regular journaling and light review prep.
Heavier usage, more repos, review season.
Short, honest answers.
The work is done. Start keeping the record.
Six months from now, you’ll be glad it’s already written.