Saturday night at Twilo, somewhere around 3 AM, Sasha drops the low end out of a track and holds the room in silence for four bars. Three thousand people suspended. Nobody told them to stop moving. Nobody had to. He read the moment, and the room followed. When the bass came back, the floor hit different because the absence made the return physical. That decision had nothing to do with music. It had to do with the people standing in front of him.

I spent years in that room before I understood what I was watching. Two DJs making decisions in real time based on a single input: what the crowd needed next. What this room, tonight, at this hour, with these specific bodies, required. Regardless of the tracklist or what worked last week. Every choice was a response to something they were reading. The material happened to be vinyl, but the actual work was always about the people on the floor.

A few years later I’m in a computer lab at a public school in Brooklyn. Twelve students, twelve different processing profiles, twelve different ways of shutting down when the task doesn’t fit. One kid freezes when there’s too much text on screen. Another needs to hear instructions out loud or they vanish. A third does fine until the room gets loud, and then nothing gets through. Different material, same work.

I didn’t walk into that classroom thinking about Twilo. I wasn’t drawing connections. I was just doing the thing I apparently do: reading what the person in front of me needs and adjusting before they have to ask for it. With Eliar, that meant recognizing a disruption as protection. With the kid who froze at too much text, it meant breaking the assignment into three screens instead of one. Small adjustments. Each one specific to a single person.

Then twelve years at Encore, building educational publishing software. The person on the other end was a user I’d never meet. A teacher in a district I’d never visit, trying to get through a lesson plan with thirty kids and a platform that was supposed to help. I couldn’t read their face. I couldn’t hear their voice. But I could read their behavior: where they dropped off, what they skipped, the gap between how the feature was designed and how it was actually used. Every click pattern was a sentence. Every abandoned workflow was a paragraph. The material was code, but the work was still about the person trying to use it.

And then the kitchen. Four of us. My wife can’t do gluten. My son needs high-protein or his energy craters by 2 PM. My daughter is thirteen and will eat what she wants regardless of what I put down. I’m cooking for all four, and the only way dinner works is if every plate is a specific response to a specific person, built from the same base. One meal, four accommodations. Nobody asked me to think about it this way. But once you see every room as a room to be read, you can’t stop.

When Randi started Aiden Jae, she had the product. Solid recycled gold, genuine stones, pieces manufactured through certified partners in Bangkok. Exquisite work. But her brand wasn’t showing it. The photography was wrong. The copy didn’t match the quality. The platform fought the product instead of serving it. She knew something was off but couldn’t locate it. I could, because I could read what she was trying to say and see the distance between that and what a stranger would actually receive. The brand infrastructure needed to close the gap between what she made and what someone on the other end would feel.

I didn’t plan to end up in all these rooms. A nightclub, a classroom, a codebase, a kitchen, a jewelry brand. There’s no career path that connects them. No degree that covers the spread. But looking back across all of it, I can see one skill operating the entire time. The same instinct, applied to whatever material was in front of me.

Every room had different material. Every room had the same person on the other end of the work.