Testing in Production: The Arena, Mental Health, and Why Quality is Never Just About Code

 For over twenty years, my professional identity has been wrapped up in a single, heavy question: "Quis custodiet ipsos custodes?"—Who watches the watchers?

In the early days of the dot-com bullpens, the game studios testing next-generation engines, and the high-stress finance migrations, I wore that motto like armor. I was a kid from Santa Monica City College who minored in philosophy just to keep the tech space honest, but I still believed armor was the answer. I thought my job was to be the friction. The unyielding wall. The cynical eye that kept the company from shipping its own disasters.

I built a career on finding hidden flaws, tracing bad data paths, and forcing teams to look at what they’d rather ignore. But when you spend two decades looking for what’s broken outside of you, it becomes an incredibly effective coping mechanism to avoid looking at what’s fracturing on the inside.

Lately, I’ve been thinking about the "Arena"—that place Brené Brown talks about where you show up, stripped of armor, covered in dust, with no guarantee of success. In tech, we are terrified of the arena. We hide behind rigid processes, velocity metrics, agile ceremonies, and the polished, sanitized veneer of professional updates where everyone is constantly "thrilled to announce" their next flawless victory.

We have optimized our professional lives for zero downtime. But human beings aren't built on high-availability architecture.

We carry silent exceptions. We run on legacy trauma. We stack up internal technical debt—burnout, anxiety, the heavy weight of mask management—and we keep pushing code to production anyway. Long before I had the diagnostic words for my own hot-running brain, I learned to build internal "sandboxes"—defensive perimeters of deep imagination to survive a volatile childhood reality where the rules were unpredictable. But a sandbox is meant for isolation; the arena demands presence.

In February 2022, when the world fractured and my engineering pods in Ukraine were suddenly swapping their keyboards for flak jackets, the global software engine didn’t pause. The deployment pipelines kept running. The FedRAMP platforms kept processing critical data. It was a stark, brutal reminder that technical infrastructure is entirely indifferent to human suffering.

But Quality isn’t.

Quality is a human condition. You cannot engineer an intelligent system if the culture that birthed it is running on toxic fumes and silent exhaustion. True Quality Intelligence requires moving past the evolutionary trap of merely catching bugs, choosing instead to rewrite the social contract of code. That means building a psychological sandbox within our teams—a safe space where an engineer can raise their hand and say, "I am broken today," with the absolute trust that the system will protect their capacity, not discard them as a defective unit.

The ultimate evolution of leadership isn't building a bulletproof automation framework. It’s being willing to step into the dust of the arena, take off the armor, and acknowledge our own vulnerabilities.

If we want to watch the watchers, we have to start by taking care of them.