I build my flow state the same way I build software

The branch that sat open for three days

I remember the exact bug. A three-line fix, nothing complicated. I opened the file, and before I typed anything, Slack lit up. I answered it — it was quick, thirty seconds, tops. Then an email came in about something "urgent." Then my phone buzzed. I looked back at my editor forty-five minutes later. The cursor was blinking in the exact same spot I'd left it.

I used to beat myself up over it — more coffee, more willpower, a better to-do list. None of it stuck, because the problem was never me. My brain isn't built to reload context every ninety seconds, and no amount of trying harder changes that. What changed things was building a room where that switching just couldn't happen.

50/10

Flow isn't found. It's compiled.

I tried the classic Pomodoro first — 25 on, 5 off. It never quite fit. Twenty-five minutes is barely enough time to even load a real problem into my head, let alone solve it. So I stretched it. What I actually run now is simpler than it sounds:

• 50 minutes, one thing. No second tab open "just in case," no notifications. Just the problem and me.
• 10 minutes, actually away. Not scrolling — up, water, eyes off every screen. Let the last hour settle somewhere in the back of my head.

My setup, before I even open the editor

Clean code, clean desk, clean mind.

You can't run something heavy on a machine that's already choking on background processes — mine works the same way. So before a sprint, I run through three things, almost without thinking about it now:

• The desk: whatever isn't the task, off it. Water within reach. Light that doesn't fight with my screen.
• The screen: every tab I don't need for this exact task, closed. Do Not Disturb, on, everywhere.
• The rule I actually keep: if a question comes up mid-sprint that needs a browser, it goes on a sticky note, not a new tab. I answer it in the break, not now.

The sound underneath all of it

Music is the metronome of the mind.

The mixes I put together for the channel aren't there to fill silence. I build them the same way I'd build anything else I want to actually work: on purpose, layer by layer.

• Deep sub bass — something steady to hold onto, low enough that it never competes with what's in my head.
• No drops, no vocals — nothing that makes my brain switch to "listening" mode instead of "coding" mode.
• The association builds itself. I didn't plan this part — but after enough sessions, hitting play started doing half the work of getting into flow for me.

That's what's running in every live She Codes Studio session — melodic chillstep, deep sub bass, atmospheric synth pads, nobody talking over it. Built to hold up for a full session without ever asking for your attention back.

My cycle, on a normal day

sudo apt-get install focus

I didn't overhaul my life to make this work. I just repeat a small script, most days:

1. Pick the window — 50 real minutes, wherever they fit. Morning, after lunch, midnight, doesn't matter.
2. Name the one thing — write down, in actual words, what this sprint is for. Just that.
3. Press play on whatever's live or the newest mix.
4. Stay with it until the timer runs out. If I get stuck, I don't leave — I just breathe and keep looking at the problem.
5. Ten minutes off — I ask myself what pulled my attention this time, and quietly fix that for the next round.

I'm not trying to be productive for three hours straight anymore. Just for the next 50 minutes. Then the 50 after that. It adds up on its own.

Questions people actually ask me