Two in the morning, I've closed the laptop, but my head hasn't. The screen is dark, the room is silent, and yet inside my skull there's a server still running at full tilt, fan whirring, processing something nobody asked it to process.
It's replaying the internship interview from that afternoon. The exact moment I hesitated for half a second before answering a question. Half a second. And now, in my head, that half-second stretches the length of a century. "They must think I froze. They must think I don't know anything." Other nights it's the silly misconfiguration on the cloud that morning — one line I left out, fixed in thirty seconds — and yet at midnight it comes back the size of the whole sky.
One grain of sand. And I've blown it up into an entire desert.
My brain was trained to be afraid
I used to think this happened because I was weak, prone to fretting over nothing. But the longer I've been in this work, the more I've noticed something a little ironic: the very ability that makes me overthink at night is the ability that lets me do my job during the day.
Those of us in engineering, in design, are taught to spot what's wrong. All day I sit there scrutinizing: what if the user types nonsense into this field, which case is this flow missing, where does this form break. We call it finding bugs, thinking about edge cases. A valuable skill. It's literally what I get paid for.
The problem is that late at night, I forget to turn it off.
The brain that's used to scanning code for flaws turns, at midnight, to scanning my own... life for flaws. And life has infinite edge cases. It starts building scenarios: what if I don't get this internship, and if I don't then I'll probably fail the next round too, and if I fail that then I'll graduate unemployed, and if I'm unemployed then... On and on. A binary tree of fear, every branch leading to some bad ending.
I thought I was solving a problem. I was actually building a maze to trap myself in.
The illusion that thinking will fix it
There's a quiet belief underneath every spiral of overthinking, one it took me a long time to name: I believe that if I think long enough, hard enough, I'll control the outcome.
It sounds so logical. By day it even holds — think it through and the code really does have fewer bugs. But a human life isn't a function. I can rewind that interview a hundred times and they've already decided. The result email won't change its contents because I lost sleep. You can't debug something that has already happened.
Thinking, in the right place, is a flashlight on the path. Thinking, in excess, is an engine idling at 2 a.m. — loud, overheating, going nowhere.
What I mistook for "looking for a solution" was really just wringing myself dry. I don't wake up wiser. I just wake up more tired.
"Today was enough"
I couldn't cure this by forcing myself to stop thinking. Try ordering your brain to "stop thinking" — watch it think twice as much.
What helped me was a very short line I say to myself whenever I catch that server in my head booting up again: today was enough.
Not "everything is fine" — that's a lie, and my brain is sharp, it won't buy it. Just: today's share of the work, I've done it. The interview, I answered it. The config, I fixed it. The rest belongs to tomorrow, and tomorrow hasn't come. I give myself permission to set it down.
And I practice forgiving my own imperfection. That half-second of hesitation? They're human too, they understood. That one wrong line of config? Fixed, done. I'm allowed to be a person who sometimes stammers, sometimes mistypes. It's okay.
So if you're lying there tonight too, eyes shut but head wide open, I won't tell you to "just relax" — that's useless advice.
I just hope you can do one small thing: notice. Ah, I'm overthinking again. Just calling it by its name makes it shrink a little. Then smile at that gritty, talkative, far-too-cautious head of yours — it isn't out to ruin you, it's only trying to keep you safe in its clumsy way.
Then close your eyes. Deal with it tomorrow. Tomorrow I'll have a whole day to think, after all.