The First Cup: How I Start Every Coding Session

The Walk to the Coffee Machine#

I start making coffee before I open my laptop. Every time. It sounds like a small thing, but sitting down with a cup in front of me is what keeps me in line — it's the difference between staring at a blinking cursor and actually settling into work. I can't focus without it. The ritual of grinding, brewing, pouring gets my head into the right space before I've written a single line of code.

The part that actually pays off, though, isn't the drinking — it's the walking. When I get stuck on a bug or can't figure out how a feature should work, I get up and go refill my cup. Walking away from the screen, doing something completely unrelated to the problem, is usually what cracks it open. It's the same thing people mean when they talk about "shower thoughts" — the solution shows up right when you've stopped actively looking for it.

The Boundary Before Focus#

I won't open my laptop before the kettle's on. That's not superstition, it's a boundary. Sitting down with coffee in front of me is what puts me into focus mode, and having a clear ritual to trigger that switch matters more than I expected it to.

I've learned that focus sessions need a length that isn't too short and isn't too long — go too long without a break and it wears me down over time, not just that day. Coffee gives me a natural way to step in and out of focus mode without losing the thread completely. A cup, a refill, a short walk — each one is a checkpoint, not a distraction.

When the Ritual Breaks#

I can feel it immediately if I don't get that first cup before starting my day, whether I'm at the office or working from home. And it's not really about caffeine — I drink decaf just as often. It's that skipping the ritual puts my head in a state it isn't used to for doing this kind of work. The mental switch never gets flipped, and the whole session feels off before it even starts.

That's the part that surprised me most once I paid attention to it: how much of "being ready to work" isn't something I just have. It's something I build, every morning, the same way.

Dialing In#

The reason sitting down with that first cup works as well as it does is routine, plain and simple. I've been doing this long enough that it's become the natural way I start a coding session — not a hack I'm trying, just how it's done now. Without it, I genuinely struggle to focus.

It's a small, low-stakes loop, not unlike debugging: the same input, the same conditions, checked against the same expected result, day after day, until it's not something I think about anymore. It just works, because I've run it enough times to trust it.

A Discipline I Didn't Choose on Purpose#

I don't think coffee should run anyone's life, mine included. This is just the routine I happen to be built around. Other people use a glass of cold water, a smoke break, a walk around the block — the specific ritual doesn't matter much. What matters is having one.

Routines are what keep us in line. They're what get us through the workday, and, if I'm honest, they show up everywhere else too — the same patience that gets me through a hard debugging session is the same patience that gets me through a difficult class on the mat. I didn't set out to build my life around routine. It just turned out that's what was working the whole time.