same service, different ports.
on holding builder and healer as one thing, not two. a note to myself.
for most of my twenties i thought i had to choose.
either the london startup — frontend lead, cto twice, shipping code at 3am — or the other one, the one that kept pulling: ceremony, breath, the sound of a gurmukhi mantra at 4am in kashmir. they were on different continents, different timelines, different kinds of attention. they were, i believed, two different jobs.
they were not two different jobs.
the misread
the mistake was treating them as separate processes. builder over here. healer over there. one paid, one didn't. one made things you could deploy; the other made things you could only witness.
years of running both in parallel, not knowing they were the same.
then one morning in mazunte, sitting at my desk with claude code open and a kid screaming in the next room, the frame broke. what i do when i build is what i do when i sit. i listen to what's happening. i notice where the friction is. i move the blockage. i wait for the right sequence. i don't force.
the difference isn't the work. it's the port the work listens on.
same process, different port
think about it like this. a process running on a server can expose itself through many ports. http on 80, ssh on 22, websockets on 443. the process itself doesn't change. what changes is the protocol through which you reach it.
my work is one process. sometimes it listens on the port called engineering — you reach it by writing a brief, by opening a repo, by asking a question in code. sometimes it listens on the port called healing — you reach it by showing up scared, by asking a question in tears, by needing someone to sit with you.
the logic inside is the same. i am paying attention to what wants to happen next. i am removing what's in the way. i am not imposing an outcome. i am making room for the thing to move.
why this matters now
AI is forcing a lot of people into this realization whether they like it or not.
the engineer who thought her value was writing code finds that code writes itself. the coach who thought her value was empathy finds that GPT does a decent imitation. both get a wake-up call: the value was never the output. it was the attention behind the output.
the attention doesn't automate. the listening doesn't automate. the knowing when to push and when to wait — that doesn't automate.
that's the process. the output is the port. you can swap ports. you can't swap the process.
what i tell clients now
when someone asks me if i'm a consultant or a coach, an engineer or a practitioner, i tell them: the same service, listening on different ports.
you bring a codebase, we open port 443.
you bring a fear, we open port 22.
you bring an idea and a life stuck around it, we open both.
the work doesn't care. the work is what's underneath.
---
filed under: identity · mazunte, 2026-04