The second English piece from "Psychology of the Keyboard," a series I write about the mental side of being a programmer — the part nobody puts in the documentation.
It was around three in the morning. I'd been in front of the screen since nine at night, staring at the same line of code for what felt like the hundredth time. The function looked perfect on paper — no visible issue — but the result kept coming out wrong. I tried everything I could think of: changed the condition, dug through Stack Overflow, asked an AI. Nothing changed.
I still remember exactly what I felt in that moment. It wasn't physical tiredness. It was something else entirely — a feeling that I wasn't good enough, that maybe the problem was in my own head, not in the code. That if my colleagues saw me stuck like this, they'd assume I was a beginner, not someone running a company that builds systems handling real data.
That's the thing almost nobody talks about in programming. We talk about algorithms, best practices, the newest framework — but nobody tells you this profession takes as much from your mental health as it does from your time.
In that moment of being stuck, something happens in your brain called tunnel vision. Your mind locks onto the same path you already tried and failed on, and keeps pulling you back to it — not because the answer is there, but because a tired brain finds it easier to repeat the same move than to open a new path. The dangerous part of that moment isn't failing. It's staying seated, convinced that continuing in the same direction is the answer — which is exactly what turns one exhausting hour into two or three wasted ones.
The fix isn't to be "strong" and push through. The fix is giving yourself real space away from the screen — even five minutes. Walk. Drink water. Look at something completely different. The mind isn't a machine; it needs to reorganize itself. And when you come back, you'll often find your eyes suddenly see something that had been sitting in front of you for two hours, unseen.
One more thing worth saying clearly: your value as a programmer isn't in solving everything fast. It's in continuing even when a lot of things don't get solved on the first try. Every professional programmer has been through the exact moment I just described. The difference is learning when to stop and when to keep going — not that they stopped getting lost altogether.
Have you had a moment like this? What actually helps you find your focus again?
