There's a specific minute I take, most nights when something's genuinely broken and I don't yet know how to fix it, before I let myself touch the keyboard again. I sit back, close my eyes, and just go still for sixty seconds or so. Not solving anything in that minute. Just refusing to let the panic write the next line of code before I do.
I didn't design this on purpose, the way you'd design a productivity system. It emerged out of necessity, during a stretch where broken deploys and uncertain months were showing up often enough that I needed somewhere to put the fear before it started making my decisions for me. I noticed, gradually, that the work I did right after that quiet minute was consistently clearer than the work I did in a straight panic. So I kept doing it, without ever really naming what it was.
I think what that minute actually does is create a small, deliberate gap between the moment something goes wrong and the moment I start reacting to it. Without that gap, fear gets to drive for a while before logic gets a turn — and fear is a genuinely terrible programmer, if I'm honest. It reaches for the fastest-looking fix instead of the right one. It skips steps. It makes you certain about things you haven't actually verified yet, just because certainty feels better than sitting in the not-knowing a little longer.
There was a specific stretch, during one of the harder financial periods I've written about before, where this quiet minute mattered more than usual. I wasn't using it to solve the uncertainty — nothing about sixty seconds of stillness changes a bank balance. What it did was give me a floor to stand on before I went back into a day that had a lot of reasons to knock me over. I don't think I could have kept making clear decisions during that stretch without something like it, some small ritual that let me set the fear down for a moment instead of carrying it into every choice I made that day.
I've come to think of it less as a trick for managing stress and more as a kind of respect for the actual difficulty of what I'm doing. Building something, especially something other people depend on, deserves a clear head, not a frightened one rushing to feel finished. The quiet minute is really just an admission that I'm not always going to arrive at the keyboard with a clear head automatically, and that forcing the clarity artificially, by rushing straight into the problem anyway, usually costs more time than it saves.
It doesn't always work perfectly. Some nights the panic wins anyway, and I catch myself making a worse decision than I would have if I'd actually sat still for the full minute instead of cutting it short. I've stopped expecting it to work every single time. What I've noticed is that it works often enough, consistently enough, that I keep returning to it — the same way any habit earns its place, not through perfection, but through being useful more often than not.
I think a lot of what gets called discipline is actually just small rituals like this one, repeated quietly enough that they stop looking like anything special. Nobody sees the sixty seconds. They see the fix that came after it, and assume it was purely technical skill that got me there. Some of it was. But underneath the fix, most nights, was just a person choosing to go still for a minute before letting the fear drive.