You already did the work.
Engineer Journal turns your GitHub activity into a record you can save, revisit, summarize, and use at review time.
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…
From commits you’ve forgotten to a record you can use.
Four steps, then it runs in the background of how you already work.
Install the GitHub App with read-only access to the repositories you choose.
Choose the repos and pull requests you want Engineer Journal to track.
Turn PRs, days, weeks, and sprints into clear, editable journal entries.
Use saved summaries to prep for reviews, 1:1s, interviews, and brag docs.
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 process PR data to create summaries, then store the summaries — not your raw code or diffs.
- 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.
Pay for a summary budget, not a PR counter.
Usage runs on a flexible monthly summary budget. Larger reviews and historical backfills may use more of it.
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.