OLD SCRIPT DETECTED
Try this response:
“A green square only shows a public push, not what the week actually held.”SEE THE PRACTICE
THE THOUGHT
“His contribution graph is greener than mine, so he's better than me”
YOUR RECORDED RESPONSE
“A green square only shows a public push, not what the week actually held.”
ONE PRIVATE MOVE
Open your own commit history for the past month and privately write down three things you did that a contribution graph can't show, no comparison tab open.
SCENE_01
You open his GitHub profile after stand-up, where he mentioned finishing a feature, and there it is: a wall of dark green squares running back for months, barely a gap. You click over to your own profile in the next tab. The grid is patchier — pale green, empty white weeks where you were buried in a migration nobody saw commits for. You didn't mean to compare. You just wanted to check something in his repo, and his graph loaded first.
SCENE_02
The grid reads like a scoreboard, so you read yourself as losing it. Every white week becomes proof you coasted, even though one of them was the week you walked a new hire through the auth service line by line, and another was the week you were on call and slept through half of it fixing an outage. None of that leaves a commit. So instead of mentioning what you actually did in stand-up, you start timing your own pushes — landing a tiny fix at 11pm just to paint tonight's square in.
SCENE_03
A contribution graph counts pushes to public branches, not usefulness — it can't see code review, incident response, mentoring, or a hard week of debugging that ended in one squashed merge. Instead of padding tonight's square, you open your own repo's commit log and skim what actually shipped this month with no comparison tab open beside it. The list is longer than the color implied.
TRACE · 01/04
SOURCE_LOCATED · 02/04
The Velocity Scoreboard
If the visible grid of green squares is lighter than his, that gap is a scoreboard proving he is the better engineer — regardless of what actually filled your white weeks, and regardless of what his own graph leaves out too.
FORGING_REPLACEMENT · 03/04
Generated per person in the app — these are the flavor, not your script. Yours is built from your exact words.
INSTALL · 04/04
When I think
“His contribution graph is greener than mine, so he's better than me”
I say
“A green square only shows a public push, not what the week actually held.”
Then I do one thing
Open your own commit history for the past month and privately write down three things you did that a contribution graph can't show, no comparison tab open.
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
It reflects more public pushes to tracked branches, which correlates loosely with output but misses code review, incident response, private repos, pairing, and any week where work landed in one large squashed merge instead of many small commits.
Some managers do glance at them, which is a reason to make your non-commit work visible in writing, like a status note or a doc, not a reason to treat the grid itself as an accurate scoreboard of your week.
Because the grid is public and instant, while your on-call, review, or mentoring hours have no comparable display. The mismatch is in what gets rendered, not in what got done.