The Comment That Ruined My Thursday

2026-11-21来源 dev.toEnglish
The Comment That Ruined My Thursday

09:12. I open the pull request and there it is, three words under a line of my code, in red.

"This is wrong."

No line number beyond the one it sits on. No "because". No "try this instead". Just the three words, and a name beside them I recognise from the team list, and a little grey timestamp that says it arrived at 08:47, twenty-five minutes before I got to my desk.

I read it again. Then I read it a third time, slower, as if the extra words might be hiding between the three that are there. They are not.

The line it sits on is mine. It sorts a list of invoices by date, and I wrote it on Tuesday afternoon, in a hurry, because the dashboard needed it and the afternoon was already gone. I remember writing it. I remember feeling clever about it for about four seconds, which is the usual length of time I feel clever about anything I write.

09:14. I click on the file. The function is eleven lines long. I read it the way you read a text from someone you like, looking for the tone underneath the words. It sorts. It returns. It handles the empty list. I check the tests. Two tests, both green, both mine. I run them again anyway, because running them feels like doing something, and they go green again, which tells me nothing except that the tests agree with me, and the tests were written by me, so of course they agree with me.

09:31. I start a reply.

"Could you say a bit more about what's wrong here? Happy to fix it."

I read it back. It sounds fine. It sounds like a person who is not bothered at all. I delete it. It sounds too fine, which is the problem. If I send that, I will spend the rest of the day wondering whether she thinks I am being passive-aggressive, and she will spend the rest of the day wondering whether I am. Nobody wins.

09:47. Second draft.

"Which part is wrong? The sort, or the date handling?"

Shorter. Honest. I hover over the button. My finger does not press it. Because what if she answers "both", and then I have to ask again, and now I am the person who needs three rounds of comments to understand one line of code. I delete it too.

10:05. Third draft, and this one is long. It explains why I wrote it this way. It mentions the Tuesday deadline. It points out that the tests pass. It has a paragraph about the date format coming in as a string from the old system, which is true, and which has nothing to do with anything. I read the whole thing and I can hear how it sounds: a man building a small fort out of excuses and sitting inside it. I select all of it and delete it, and the empty box looks back at me, and I feel better and worse at the same time.

10:40. I give up on the reply and go back to the code. This is the part of the day where I become a detective in my own flat, looking for something I lost in a room I cleaned myself.

Maybe it is the sort. The dates arrive as strings, "2026-11-04", "2026-11-19", and string sort works fine on those, until it doesn't. I think about it. It works fine. I think about it more. It still works fine. I think about it until "works fine" starts to sound like something a person says right before finding out it doesn't.

Maybe it is the empty list. Maybe it is the duplicate dates. Maybe it is the fact that I named the variable sorted and shadowed something somewhere. I open the file that calls this function. I open the file that calls that file. By 11:20 I have five tabs open and I am reading code I wrote last month as if it were written by a stranger who might have left me a clue.

11:58. I close the tabs. I have found three things that might be wrong, and I am not sure about any of them, and the honest truth is that I could rewrite the whole function in twenty minutes and still not know whether I fixed the thing she meant. I eat lunch at my desk, which I never do, because leaving the desk feels like leaving the argument, and the argument is only happening in my head, and I cannot leave my head.

13:20. I check the thread. Nothing new. The three words are still there, patient as a parked car. I read them again and this time I notice the full stop. "This is wrong." The full stop makes it worse. Without it, it could be a thought she typed quickly. With it, it sounds finished. Settled. A verdict with nowhere to go.

13:44. I open the reply box again. I type "Thanks for catching this —" and stop. Thanks for catching what? I do not know what she caught. I am thanking her for a mystery. I delete it.

14:15. I do actual work for an hour, or I pretend to. I fix a typo in a readme. I rename a variable in a file nobody will ever open. I answer two messages with unusual speed, because answering messages is a thing I can complete, and the comment is a thing I cannot. Every ten minutes I click back to the pull request, the way you check a phone that has not buzzed, and every time the thread is the same, and every time I am a little annoyed at myself for checking.

15:30. I write the reply I should have written at 09:14. Six words.

"What part is wrong? Happy to fix."

No explanation, no defence, no "thanks for catching this". Just the question, asked plainly, the way I would ask it if she were sitting next to me and I had not spent six hours making it complicated. I press the button before I can re-read it. The page reloads. My question sits under her comment, small and a little bit naked, and there is nothing to do now except wait, which turns out to be its own kind of work.

16:02. She is online. I can see the little dot. I watch the dot the way you watch a kettle. The dot stays. Nothing arrives. I open another file and stare at it without reading it.

16:41. The reply comes. Two lines.

"The sort compares the strings, so the 9th sorts after the 19th. Compare the timestamps instead."

I read it twice. Then I laugh, out loud, alone, at my desk, because of course. Of course it is the dates. The strings sort fine until the day number hits double digits and then "9" sits after "19" like it owns the place, and every invoice from the first nine days of the month has been sitting in the wrong order for a week, and the tests passed because both my test dates were in the twenties. A four-minute fix. A four-minute fix that cost me a Thursday.

16:47. I change one line. I compare the timestamps. I run the tests. Green. I add a third test with a date on the 9th and a date on the 19th, because that is the test I should have written on Tuesday, and it goes red before the fix and green after, which is the sound a test is supposed to make. I push. I write "Fixed — sorting by timestamp now, added a test for single-digit days." I press the button. The thread closes itself in my head the way a door closes when you finally stop holding it open.

17:20. The rest of the day is quiet. The quiet is the strange part. The comment is answered, the code is fixed, and there is nothing left to be angry about, which leaves me with the anger and nowhere to put it. I keep thinking about the six hours. Not the bug. The bug was four minutes. The six hours were mine. I spent them writing replies I never sent and reading code I had already read, because three words with no "because" felt like a verdict, and I treated it like one, and a verdict is something you defend yourself against, and a question is something you just answer.

18:35. A pull request from someone else lands in my queue. A new joiner, three weeks in, and I open it, and I read it, and I find the thing that is wrong. It is a small thing. A loop that runs one time too many. I click on the line. The comment box opens, empty and patient. I type "this is wrong" and I look at it, sitting there in the box, three words and a full stop, and I delete it.

I write the other version instead. The line number, and what it does wrong, and what to change, and the two minutes it will take. I read it back and it sounds like a person who wants the code fixed, not a person who wants to be right. I press the button. The comment goes out with my name beside it, and the thread waits, and somewhere on the other side of it a person is about to have a much shorter Thursday than I did.

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

Buy me a coffee

AheadKit on Gumroad — Beginner-Friendly Books & Packs

原文:https://www.a8q9.cn/en/article/the-comment-that-ruined-my-thursday-24c9eb.html

相关文章