All writing

What I Listen to While Coding

For a few years my answer to this was lo-fi. There’s a whole genre engineered for it now: a cartoon girl studying at a desk in an endless loop, the same warm downtempo beat for hours. For a while it did the job. Then it didn’t. At some point the beats stopped helping me focus and turned into the thing I was half-listening to instead of working. My taste drifted somewhere stranger after that, and the drift is what taught me what I was actually after.


The Only Rule Is No Words

The one principle I’d stand behind: no lyrics.

Reading and writing code is a language task, and lyrics compete for the same part of your head. The moment a track has words I can make out, some small background process starts parsing them, and that’s attention I wanted for the problem in front of me. Everything else, the genre, the tempo, whether it’s officially “focus music,” is just preference. Even this rule has an exception, which I’ll get to.

I went through the binaural-beats phase too, back when draft of this post first existed. I’m not going to tell you that 40Hz unlocks your gamma-wave creativity, because I don’t believe it and I honestly couldn’t tell the difference. There’s a small industry selling engineers neuroscience-flavored focus audio, and if a given app works for you, good, but I’d hold the brain-science claims very loosely. None of what follows is optimization. It’s just what I like.


What I Actually Put On Now

These days it’s mostly post-rock and drone, plus a few other wordless and frankly weird corners.

Post-rock is rock instruments used for texture and dynamics instead of hooks and choruses. Long instrumental pieces that build slowly, crest, and fall, often ten minutes at a stretch, which has a practical upside: I’m not making a track-change decision every three minutes. It carries momentum without ever asking me to pay attention to it. The usual on-ramps are the obvious ones if you’ve never gone looking, but the genre is deep and worth wandering in.

Drone is the same idea taken further. Sustained tones and slowly shifting texture, almost no rhythm or melody, closer to weather than to songs. It’s basically brown noise with taste. On a hard debugging session that’s exactly what I want: something that fills the room and masks the world without putting a single idea into it.

The shared property, the thing both genres have that lo-fi eventually lost for me, is that they surround the work instead of interrupting it. They’re a space to think in, not a thing to listen to.


The Exception: When I Want Energy, Not Quiet

Sometimes the work doesn’t need flow. It needs momentum. A tedious migration, a wall of boilerplate, the end-of-day push when the focus is gone and I just need to keep moving and shipping.

That’s when I break my own no-lyrics rule on purpose and put on something loud with words. Opeth, Sabaton, Hammerfall. Half nostalgia, half caffeine. Power metal in particular is gloriously over-the-top, and that’s the entire point: nobody writes a miserable migration script while a song about a historical cavalry charge is going. It doesn’t help me concentrate. It helps me not stop.


Why It Works

The honest version of all this isn’t that the right audio makes me measurably more productive. I have no numbers and I don’t trust the ones other people cite.

It’s that putting on the right thing is a switch. Headphones on, the world narrows, and some part of my brain accepts that it’s time to work. The specific sound matters less than what it signals, which is probably why I could ride lo-fi for years and then drop it the moment it stopped feeling like a signal and started feeling like noise.

One warning, the same one I’d have given years ago: pick carefully what you pair with a big project. Loop one album through three months of a brutal codebase and you will not be able to hear it again without flinching.

Email address copied hello@darkotasevski.dev