← All posts

Mixing consoles and microservices — one discipline, two crafts

People ask how I context-switch between leading an AI engineering org and recording Sufi-rock covers at midnight. The honest answer: I don't. It's the same job at different frequencies.

Both are systems that must disappear

A great mix is one you don't notice. Nobody leaves a concert saying "excellent gain staging." They say the song moved them. Great infrastructure is the same — nobody praises your Kubernetes topology; they notice the product never made them wait.

In both crafts, the work succeeds by vanishing. Every fader move and every service boundary exists so the person on the other end feels one thing, not many things.

Headroom is the same idea everywhere

In audio, you leave headroom so a loud transient doesn't clip. In systems, you leave capacity so a traffic spike doesn't page you at 3 a.m. Same principle, same failure mode when ignored: everything is fine until the one moment that matters most, and then it distorts.

I budget headroom in orgs too. A team running at 100% utilization clips exactly like an overdriven channel — the damage shows up downstream, in places you didn't mic.

Arrangement is architecture

An arrangement decides which instrument owns which frequency band so they don't fight. Service architecture decides which system owns which responsibility so they don't fight. When two services both think they own user state, you get the same mud as two guitars fighting over 2kHz. The fix is identical: someone has to decide, explicitly, who owns what — and then everyone commits to the arrangement.

Rehearsal is CI

Bands that only rehearse the whole song fall apart on stage. Tight bands loop the transitions — the four bars where things go wrong. Good engineering teams do the same: they don't just test the happy path, they rehearse the failure transitions. Deploys, rollbacks, incident handoffs. The transitions are the performance.

The one real difference

Software wants to be correct. Music wants to be true. A system either meets its contract or it doesn't; a vocal take can be pitch-perfect and dead, or slightly rough and devastating. Spending my nights in a discipline where "technically right" isn't the goal keeps me honest in my days — because products, like songs, are judged by what people feel, not by what the dashboard says.

Two frequencies. One signal.

Get the monthly letter More posts