5:00 PM. Laptop closed. Slack closed. Workday over. Except my brain didn't get the memo.
I'm making dinner, and I'm still half-thinking about a fu...
For further actions, you may consider blocking this person and/or reporting abuse
My shutdown process is simple, say goodbye to my online collegue, then close my woking laptop down, say how are you? to my wife and thats all.
I like that. Maybe the best shutdown ritual isn't another productivity system at all it's simply having a clear moment where you stop being a developer and start being yourself again. 😄
Your shutdown list stopped me, because I recognized it line by line: what the problem is, what you already know, the specific next action, current status. That's not just a wind-down ritual - it's the exact schema of a good engineering lesson, and you've derived it from sleep hygiene instead of from incident reviews. Same shape, two directions.
Your question, honestly answered: the last problem that followed me home was a monitoring check that reported green over an empty dataset - the mean over zero measurements is zero, so "nothing measured" looked identical to "nothing wrong". It followed me around for an evening precisely because it wasn't written down yet; the loop closed the moment it became a note with a next action, not when it was fixed (that took two more days, and slept fine).
One addition from having institutionalized your ritual: writing it down only releases the loop if you TRUST the place you wrote it to come back to you. A note nobody re-reads calms you for one evening; the brain learns the trick and stops believing it. What made it stick for us was pairing the shutdown ritual with its mirror - the startup ritual reads yesterday's notes first, every time, so the capture provably survives the night. The door closes because you've watched it open again.
Curious about your last line, because it's the hard part: "deciding which unfinished thing is genuinely allowed to wait" - do you have a working criterion for that, or is it still judgment call by judgment call?
The exact schema of a good engineering lesson, derived from sleep hygiene instead of incident reviews is a better description of what that list actually is than anything I wrote. I hadn't consciously connected it to a postmortem template, but you're right, it's the same shape: what happened, what we know, what's next, current state. same discipline, aimed at your own head instead of a shared doc.
the monitoring bug is a genuinely good example of why some problems follow you home specifically. "mean over zero measurements is zero isn't a bug you can un-know once you've seen it, and it's the kind of thing that keeps quietly nagging precisely because it's conceptually simple and still wrong in production. the detail that it followed you for an evening and stopped the moment it became a note, two full days before it was actually fixed, is the clearest possible confirmation of the article's actual claim. the loop closes on capture, not on resolution.
the addition about trust is the real gap in what I wrote, and I think you're right that it's the harder half of the problem. a shutdown ritual without a startup ritual reading it back is just a diary entry. the brain isn't wrong to stop believing the note if nothing ever proves the note survived the night. pairing the two, so the door closing is provably paired with the door reopening, is a more complete version of this than what I described.
honest answer to your actual question: still mostly judgment call by judgment call, no clean criterion. the closest thing I've got isn't a rule, it's a question: does this get meaningfully harder or riskier if it waits until tomorrow. most things don't. the ones that do are usually the ones with a blast radius that grows while you sleep, which is a different category than most bugs, that mean-over-zero one included, since it was wrong the whole time either way.
"Does this get meaningfully harder or riskier if it waits until tomorrow" is more of a criterion than you're giving it credit for. It cleanly separates two classes: things that are wrong and getting worse (blast radius grows overnight), and things that were wrong the whole time - your framing of my mean-over-zero bug, which had been wrong for weeks and could safely stay wrong until Thursday. Judgment call by judgment call, but the question does the sorting.
On the startup half: the one mechanic that made read-back stick for us is brutal and small - the note must lead with the single fact tomorrow-you needs, in the first line, because morning-you skims. A note that starts with backstory is a diary entry wearing a to-do's clothes. The door-reopening ritual is mostly a formatting discipline on the door-closing one.
And: "the loop closes on capture, not on resolution" - if I ever write the startup-ritual half of your article, I'd like to quote that line with your name on it.
Fair you're right, it does more sorting than I gave it credit for. wrong and getting worse versus wrong the whole time either way is a cleaner split than judgment call implies, even if applying it is still a judgment call each time. a criterion that sorts two categories correctly is still a criterion, I was underselling my own line.
a note that starts with backstory is a diary entry wearing a to-do's clothes might be the single best sentence in this entire comment section. and it's a genuinely actionable fix, not just a diagnosis, lead with the fact tomorrow-you needs, not the story of how you got there. that's a formatting rule I can actually apply starting tonight.
and yes, obviously, quote away. that line came out of trying to describe what your monitoring bug story actually proved, so it's really yours as much as mine at this point.
The trade stands then - your diary-in-to-do's-clothes for my two-category split, both quoted with names on, and tomorrow-you gets the fact first. That's the whole thread in one formatting rule.
Guilty of this. Been coding very late until 4:00AM in the morning just because I like to code, it's addicting. I even shared it in Virtual Coffee and got the same advice to rest first:
But yeah, you are definitely right. We don't want to end up in an endless
whileloop without any condition to break out of it. Great read.Haha the while true energy is real. Honestly it's addicting is the most relatable part of your comment, that's exactly why willpower alone doesn't fix it, the same reason bugs stick in your head is the reason 4 AM feels fine in the moment. Good that Virtual Coffee called it out though, sometimes you need someone from outside your own head to say it. Get some sleep 😄
Refreshing article & how you broke down the biology behind the unfinished loop = 👍. I'll add this piece: In software, 'done' is an illusion, and peace of mind comes from managing your attention, not your output. 🫡
Not often but some nights I just DND and sleep 🥱
Exactly. I really like that distinction peace of mind isn't always about finishing everything, it's about deciding what deserves your attention right now. And honestly, some nights “DND and sleep” is the most productive decision you can make. 😄
my way of shutdown is "let it go~ let it go~ i dont want to see this anymore~" turn off wifi, turn off laptop and go do other stuff
Honestly Let it go might be the most effective shutdown ritual I've heard so far. Wi-Fi off, laptop off, and absolutely no negotiating with your developer brain. Sometimes the best way to close the loop is to stop trying to close it.