This post shows how to use your git history to write a self-review with facts.
In the performance series I said team metrics do not belong in a review. This is different: your own numbers, used by you.
The problem
In a yearly review, people write about recent work and forget the first months. Without data, the manager fills the gaps with impressions.
A brag document fixes this. Julia Evans wrote about it . Most people stop writing it in February. Git already has the data: every PR has a title, a date, a size and a reviewer.
What a good claim looks like
A good claim has three parts:
Claim. What you did, in one sentence.
Number. A fact anyone can check.
Story. Why it mattered.
Weak: "I helped a lot with code reviews."
Strong: "I reviewed 246 PRs from other people, up from 160 last year. Most were in payments-api. My median first review came 2.6 hours after a PR opened."
Numbers are not a score. Use them to find your stories.
Step 1: compare this year with last year
I use ShowOffer .…