Blog1 min read
Music for debugging
Writing is forward motion; debugging is search. The music for it has very little event.
Debugging is a different cognitive task from writing code, and the music for it is slightly different too. Writing is forward motion; debugging is search. You're holding more state in your head — the assumed truth, the suspicious truth, the actual truth — and any music that asks for attention costs you one of those slots.
What works is something with very little event. Long drones, slow ambient pieces, minimal piano. The lo-fi room is mostly too eventful for serious debugging — the regular beat structure that helps you write code is exactly what breaks the trance of stepping through a stack trace. Focus-room music, leaning toward the slowest end, is what fits.
What I avoid is anything with a hook. A melody you'll catch yourself humming costs the most expensive thing in debugging, which is the held assumption. Once you've forgotten what you were testing, the bug wins another twenty minutes. Texture survives this; melody doesn't.
Once the bug is found, the music can come up again. The hour after a debug is one of the few hours where any music sounds great — the brain is relieved, your shoulders come down, you can put on something with a lyric and feel like a person again. Reward your nervous system. It earned the lo-fi.