Forty hertz sits near the bottom edge of what human ears register, and it's low enough that most laptop speakers can't reproduce it at all. They flatten it into nothing before it ever reaches you.
That's the frequency underneath what a certain corner of the internet calls the Genius Song: a long, droning focus-audio track that a lot of remote developers have folded into their deep work routine, right alongside noise-cancelling headphones and a phone left in another room. Binaural beats get filed in the same mental folder as scented candles and self-help apps, and I get the skepticism — a friend of mine leads weekend rock climbing sessions at Portland Rock Gym and thinks the whole hum-in-your-ears thing is nonsense. Fair, honestly. But cognitive performance on a genuinely hard logic problem is a fragile thing when your office doubles as your living room, and this is the one experiment that actually stuck after I dropped every other gadget I tried.
What the Genius Song Actually Is
It isn't a song in any normal sense — no verses, no hook, just a sustained tone loop built around that 40Hz frequency, sometimes layered under rain or white noise. People connect it to brainwave entrainment, the idea that a steady external rhythm can nudge your brain toward a state suited to focus, but I'm not a neuroscientist and I'm not going to pretend I can explain the mechanism with any authority. What I can tell you is what changed once I swapped playlists with actual songs for this instead: nothing dramatic, just less friction. Coding at a certain difficulty level asks for continuity, not stimulation, and this track is boring in a way that stops competing for your attention.
A Reader Asked: Ritual or Real?
A reader named Tarkan Wesolowski emailed through the site's contact form a while back — four sentences, somehow containing everything relevant, which is its own rare skill. His question, paraphrased: is this actually doing something, or is it just an elaborate ritual that happens to coincide with him sitting still long enough to concentrate?
Honestly, both things can be true at once. Some of what the Genius Song does is genuinely about consistency — no shuffle, no surprise key change, nothing for your brain to flag as new information competing with the bug you're chasing. Some of it is ritual, the same way tying your shoes signals "we're doing this now." The useful distinction isn't real-versus-placebo, it's whether it's doing anything for you specifically: if your workspace is already quiet and your baseline focus is fine, you probably won't notice much difference. If you're working through the kind of ambient noise that comes with sharing a home with other humans, that's where it tends to earn its keep.
I track this kind of thing the way I'd track any self-experiment: baseline first, one variable at a time, logged in Notion so I'm not just trusting vibes a few weeks later. It's also worth separating actual brain fog from plain avoidance, because those two get mistaken for each other constantly, and the fix for one does nothing for the other. A standing desk converter taught me that the hard way: I used it for exactly eleven days before quietly reverting to sitting, because my problem was never posture.
High-Tempo Playlists Work Against Deep Work
High-tempo tracks were my default for years — the theory being that fast music would somehow overclock the brain to match it. Wrong, or at least wrong for the kind of work I do. Your ears end up parsing rhythm and lyrics at the same moment your working memory is trying to hold an entire data structure in place, and that's not free — it's the same kind of cost as any context switch, except your brain doesn't log it as one, so you just end up tired without knowing why.
Switching to something with no tempo to track and no lyrics competing for the language part of your brain removed that tax almost entirely. It's not that the low hum makes you smarter. It's that it stops asking anything of you, which turns out to be the entire point when the actual task already demands more focus than my Slack notifications get from me most afternoons.
Headphones or Speakers?
Speakers lose here, pretty much every time. A frequency this low needs real drivers to reproduce cleanly, and most laptop and desktop speakers just aren't built for it — you get a thin approximation at best. Over-ear headphones also give you something speakers can't: a physical seal that blocks a neighbor's leaf blower or a housemate's phone call, which matters more than people expect. The pressure of the cushions becomes its own signal, a small ritual that tells your brain the workday has actually started.
Loop length matters more than it sounds like it should. I stopped shuffling tracks entirely and settled on one long loop instead, because a tempo or key change resets your sense of how much time has passed, and that's exactly the kind of interruption you're trying to avoid. Pick something long enough to outlast your actual work block, so you're not restarting the ritual every ninety minutes.
None of this replaces the physical side of the equation — I've written before about building a deep work zone in my living room office, and the audio is really just the last layer on top of that. I also learned to keep my phone out of reach during these blocks, because no frequency competes with a notification. The same logic applies to your browser: cutting down the number of open tabs does for your visual field what the Genius Song does for your ears — one less source of noise your brain has to filter before it gets to the actual problem.
The Limits of a 40Hz Track
This isn't going to fix a day wrecked by back-to-back video calls — the specific fog that piles up after your fourth Zoom in a row is a different problem, and audio alone doesn't touch it. Timing supplements around your actual routine is its own puzzle, one I've picked apart elsewhere. And if you want the ingredient-level breakdown of what's actually in a typical focus stack, that lives in a different post entirely — this one's just about the sound.
There's also a real difference between what gets you into flow and what keeps you parsing something as dense as a legacy schema without losing the thread, and those are genuinely separate questions worth answering on their own terms. I've written about how I use the brain song to stay focused during 4-hour coding sprints, which covers the sprint side of things; this is more about the specific ache of complex logic. What convinced me this wasn't just ritual was coming back to a codebase after a weekend off and picking the whole context back up without re-reading a single line, the way you'd hope but rarely expect.
None of this fixes a genuinely bad day. Some afternoons the right move is closing the laptop and walking Wildwood Trail in Forest Park until the problem stops feeling urgent, and no frequency substitutes for that. But on an ordinary day, with a hard problem and a loud-enough apartment, the low hum is the cheapest, least fussy tool I've kept around. If you try it, judge it against a real baseline — your normal setup for a stretch of ordinary workdays, then this instead for a similar stretch — rather than against how it made you feel on day one.