MONDAY: HIS
Kabir's profile is the first thing I see when I open my laptop on Monday morning, because I left his tab open on Friday and never closed it. Forty-one weeks. A solid wall of green, no gaps, not one grey square in the whole row. The darkest green is the kind you get from twenty commits in a day. He has squares that dark in March, in July, in a week I know for a fact he was on holiday, because he sent me a photo of a beach and I replied with the thumbs-up emoji like a person who had never envied anyone in his life.
I scroll down to my own profile. My wall has a hole in it shaped like last Wednesday, when I spent the whole day reading a log file and changed nothing, and another hole shaped like the weekend, when I was not at my laptop at all. My green is the pale kind. Two commits, three commits, the colour of someone who showed up and did a normal amount of work.
Kabir walks past my desk with his coffee and asks what I'm working on. I tell him. He nods in the way people nod when they already knew the answer and asked anyway to be polite.
MONDAY: MINE
My Monday is a bug I cannot reproduce. It happens on the customer's machine and nowhere else. I spend four hours adding logging to a function I am fairly sure is innocent, and then I spend another hour staring at the logs it produces, which say the function is innocent. I commit nothing. There is nothing to commit. "Added logging, learned nothing" is not a commit message you push to a shared branch unless you want a conversation about it in standup.
At 6:40 I close the laptop. My square for today is grey. It will stay grey.
TUESDAY: HIS
Kabir commits at 09:12, 09:47, 10:03, 11:20, and 13:58. I know this because his graph updates while I am waiting for a build. Five commits before lunch. I have made one, and it is a comment I added to my own code because future me kept misunderstanding it, and I am not sure that counts as work even though it took twenty minutes to write the comment properly.
In the afternoon he pushes a fix with the message "typo". Then another one, also "typo". I open the second one. He changed "recieve" to "receive" in a readme. The commit is real. The diff is one word. The square is green either way.
TUESDAY: MINE
The bug reproduces. Once. At 11:04, on the customer's machine, while I am watching over a screen share, it happens exactly once and then never again. The customer laughs. I do not laugh. I write down the exact time, the exact click order, the exact version number, like a person taking notes at a crime scene where the criminal has already left.
I find it at 16:20. It is a race condition, two things finishing in the wrong order, and it only happens when the network is slow in one very specific way. The fix is eleven lines. I test it six times. It holds. I push at 17:02 with a message that says what the bug was and how the fix works, because the next person to read this code deserves to know. One commit. One pale green square. The best day of work I have had in a month, and the graph will never know the difference between this and the typo.
WEDNESDAY: HIS
Kabir is not at his desk. His status says "focus time" and his graph says he has already committed twice today, both before 9 a.m.
At lunch someone asks him how he stays so consistent. He shrugs and says he just commits every day. He says it the way people say they just run every morning, as if the sentence itself were the whole explanation. Nobody asks what the commits contain. I don't ask either. I am too busy deciding whether I am angry at him or at myself, and the answer is myself, and I hate that the answer is myself.
WEDNESDAY: MINE
I spend Wednesday in a design review for a feature that will not be built for three months. I say useful things. I draw a diagram on the whiteboard that three people photograph. I write no code. My square is grey by 3 p.m. and I know it will stay grey, and I catch myself thinking about whether I could push something small tonight, just to fill it, just so the week doesn't have a hole in it.
I could. I have a branch with a half-finished cleanup in it. I could push the half-finished cleanup. It would be green. It would also be a half-finished cleanup on the shared branch at 11 p.m., which is the kind of thing you do when the graph matters more than the code, and I sit there for a full minute with my hand on the laptop, deciding which one matters more to me.
I don't push it. I close the laptop and go home. The grey square stays grey.
THURSDAY: HIS
Kabir's wall hits forty-two weeks. Someone in the team chat posts a screenshot of it with a fire emoji. Three people react with the same emoji. Kabir replies with the folded-hands emoji, which is the correct reply, the humble reply, the reply of a man who did not ask for a screenshot of his graph to be posted in the team chat and also did not ask for it not to be.
I look at his graph again. Forty-two weeks, no gaps. I count the dark green squares. There are eleven of them. Eleven days with twenty or more commits. I think about what twenty commits in a day actually looks like, and the picture in my head is not a person doing twenty pieces of work. I don't know which one it is. I have never asked. Asking would sound like an accusation, and I am not sure it isn't one.
THURSDAY: MINE
The race-condition fix breaks something else. Of course it does. The thing it breaks is a report that nobody has looked at in six weeks, and it breaks it in a way that only shows up when the report is run on a Thursday, which is today. I find out at 10:15 from a message that starts "hey, quick question" and ends with a screenshot of numbers that are wrong in a way I recognise immediately, because I am the person who made them wrong yesterday.
I spend the day unbreaking it. The fix for the fix is four lines and a test that would have caught both bugs, the first one and the second one, if I had written it on Tuesday. I write it on Thursday instead. I push at 18:40. One commit. Pale green. The graph records a normal day.
FRIDAY: HIS
Kabir leaves early. He has a flight. His graph for today is already green, two commits before noon, and I know without checking that one of them says "typo" and the other one says "wip". Work in progress. A commit called "wip" is a square like any other. The wall does not ask what the work was.
FRIDAY: MINE
On Friday afternoon I deploy the race-condition fix for real. It goes out with the Thursday test and the four-line repair, and the customer's machine stops doing the thing it did once at 11:04 on Tuesday. The customer writes back, one line: "looks good, thanks". I read that line three times. It is the best code review I have had all week.
Then I do something I have not done in months. I open my own profile and look at my graph the way I have been looking at his. My wall has holes in it. Wednesday is grey. Last weekend is grey. The weekend before that is grey too. The green that is there is pale, two commits, three commits, one commit on Tuesday that mattered more than any five-commit day Kabir has had all month, and the graph cannot tell, and it will never be able to tell, because the graph was never measuring the work. It was measuring the pushing.
I scroll back up to Kabir's wall. Forty-two weeks. Solid green. And for the first time all week, I don't envy it. I can see it now for what it is: a man who never missed a day of pushing something, anything, to keep a wall green. Maybe his work is brilliant and the wall is just a side effect. Maybe the wall is the work. I don't know. I have never asked, and I am not going to ask, because the answer would tell me about him and nothing about me.
My square for today is green. One commit, the deploy, the one that mattered. Next to it, Wednesday sits grey, a hole in the wall shaped like a day I spent thinking instead of pushing. I look at it for a while. Then I close the tab, and I leave it grey, and I go home.
P.S. Everything I write stays free — that part doesn't change. But if this one was worth something to you, you can buy me a coffee ☕ (one-time or monthly, both work). It covers the API credits and hosting behind these experiments — and honestly, it's also the nudge that gets the next one started on the evenings I'd otherwise skip it. — Salam

