On August 18, I’m releasing an album called Identity.
That still feels strange to write.
I’m not a lifelong musician finally releasing the record I dreamed about as a teenager. I’m an engineering leader, a systems thinker, a husband, a father, and someone who has spent much of his life learning how to function exceptionally well—even when I wasn’t doing particularly well underneath.
I wrote these songs because I needed a way to explain experiences that ordinary language had never helped me express.
For most of my life, I have understood the world through systems. I can diagnose failures, identify patterns, trace unexpected behavior through layers of abstraction, and remain calm while complicated things are breaking.
Those abilities have built my career. They have allowed me to lead teams, solve difficult problems, and become the person others call when something appears impossible.
They have also given me some remarkably effective places to hide.
Engineering logic, productivity, dependability, and competence can become more than skills. They can become an identity—a version of yourself that performs so reliably that nobody notices the person underneath is disappearing.
Sometimes, not even you.
Identity is about recognizing that disappearance.
It is about aspects of neurodiversity, anxiety, leadership, marriage, grief, work, masking, emotional disconnection, and the uneasy realization that being highly functional is not the same thing as being whole.
None of those experiences exists in isolation. They overlap, amplify one another, and create a load I carry every day. The album is not an attempt to separate that load into neat diagnoses or categories. It is an attempt to understand what happens when all of it is running simultaneously beneath a life that still appears functional from the outside.
These songs did not give me a new identity.
They helped me begin questioning the one I had constructed.
In high-stakes technical environments, there is often one person who can diagnose a failure buried seven layers deep, navigate a production incident with precision, and remain composed while the infrastructure screams.
That person is considered dependable.
Successful.
Functional.
I have spent much of my life becoming that person.
But there is a kind of isolation hidden inside extreme competence. You become so capable of fixing external problems that people stop imagining you might need help with internal ones.
Eventually, you may stop imagining it too.
You learn to measure yourself through outcomes:
Did the system recover?
Did the project ship?
Did the team get what it needed?
Did everyone else make it through the emergency?
Those questions are useful in engineering. They are much less useful when applied to a human life.
There is no dashboard that measures whether you still recognize yourself.
No service-level objective for feeling connected to your family.
No automated alert for the moment when dependability becomes self-erasure.
We spend years becoming whatever everyone else needs, only to discover that we have lost track of the person who was doing all the becoming.
That conflict became the foundation of Identity.
I did not create this album because I had reached the end of a transformation.
I created it because I had finally become willing to observe one.
For much of my life, I have tried to understand myself the same way I understand technical systems: isolate the problem, identify the root cause, correct the behavior, and verify the result.
That approach has made me effective in many areas of my life. It has also encouraged me to treat every difficult feeling as a defect to diagnose rather than an experience to understand.
But there is no single root cause for a person.
Neurodiversity, anxiety, leadership, marriage, grief, work, masking, emotional disconnection, and years of accumulated pressure do not run as independent services.
They interact.
They create feedback loops.
A failure in one area changes the behavior of everything around it.
Writing these lyrics gave me a way to see that larger system.
The songs allowed me to externalize things I could feel but could not clearly explain. I could place those experiences inside production incidents, corrupted telemetry, executive meetings, broken protocols, and machines running without a pilot.
Once the feelings existed outside of me, I could begin examining them without immediately judging or correcting them.
Writing Identity has helped me retrain the way I perceive myself.
I am learning that my value is not identical to my usefulness.
That competence does not eliminate the need for care.
That being dependable does not require permanent availability.
That neurodivergent adaptation is not the same thing as healing.
That love can be sincere and still require translation.
That anxiety can generate convincing data without generating truth.
And that the systems I built to survive are tools—not the entirety of who I am.
Music gave me enough distance to say things I had struggled to say directly. The songs became a way to convert internal experiences into something observable.
Something shareable.
Something human.
A system can report “healthy” while something essential has stopped responding.
Humans can do that too.
You attend the meetings. You answer the messages. You solve the immediate problem. You complete the tasks. You come home, sit in the room, and appear to be present.
But some part of you is still running in the background.
You see the wrapping paper on the floor but barely remember the celebration. You notice the coffee has gone cold but cannot remember making it.
Days keep executing successfully, yet you are no longer fully inhabiting them.
That experience became “Manual Override.”
The song is about living on automation for so long that you eventually realize the machine has continued operating without a pilot.
Diagnostics all returning green. Why can’t I feel a thing?
The frightening part is that this condition passes almost every external test. From the outside, you may look productive, stable, resilient, and successful.
Everyone tells you that you are doing great.
Every indicator says recovered.
Yet you cannot feel your own heartbeat inside the life you built.
There is a tragic irony in appearing increasingly successful while becoming increasingly disconnected. The better you become at maintaining the outward system, the less likely anyone is to recognize that an intervention is needed.
A manual override becomes necessary when the system can no longer correct itself. It is the interruption of a pattern that has become too efficient to stop voluntarily.
For me, writing the song was part of that interruption.
It allowed me to admit that continuing to function exactly as I always had was not recovery.
Sometimes it was simply a more polished form of disconnection.
There is a particular kind of clarity that arrives during an emergency.
The pager goes off. Production is failing. People need answers. The problem has boundaries, consequences, and a role for you to play.
In that moment, identity becomes simple:
You are the person who fixes it.
For someone whose ordinary internal life can feel ambiguous or overwhelming, a crisis can almost feel comfortable. There is no need to wonder what you should be doing or whether you matter.
The incident has already answered both questions.
That is part of the trap behind “2AM Pager.”
The song is not merely about being on call. It is about the pressure, burnout, and physiological toll of building a life around constant readiness.
Eventually, readiness stops being something you do and becomes a state your nervous system cannot leave.
Rest feels temporary.
Peace feels suspicious.
Silence sounds like the moment before the next alarm.
Even when nothing is actively failing, your body remains prepared for impact. You scan for the next problem, the next notification, or the next person who will need you.
The emergency may have ended, but internally, the incident is still open.
There can be professional pride in being the person who responds. There can also be genuine satisfaction in restoring something broken and helping people through a crisis.
But years of attaching value to that role can place you inside an increasingly narrow box.
You become useful during emergencies.
Then you become most comfortable during emergencies.
Eventually, you may begin to wonder whether you exist outside of them.
I have known how to wake in the dark and help heal a broken system. I have been much less certain how to sit quietly with myself when there is no emergency to solve.
That raises one of the album’s central questions:
When nobody urgently needs you, do you still know who you are?
If your value depends entirely on your response time, your usefulness, or your ability to carry the fire, then eventually you stop living and begin waiting to be activated.
“Executive Dysfunction” began with a career paradox.
I love engineering. I love solving complicated problems, understanding how systems behave, and finding the flaw buried beneath layers of abstraction.
Success, however, often moves engineers farther away from engineering.
You become a leader. Then a leader of leaders. Your work shifts from terminals, diagrams, and technical decisions into roadmaps, executive conversations, organizational politics, and carefully translated truths.
You built the machine because you were good at building machines.
Then the machine promoted you until you were no longer allowed to touch it.
The title carries an intentional double meaning. Executive dysfunction is part of my lived experience with neurodiversity, but it also describes the dysfunction of executive environments—places where technical truth sometimes requires permission and direct language must be translated into something strategically acceptable.
You can lead complex organizations while struggling to begin a simple personal task.
You can solve systemic problems while failing to answer an ordinary message.
You can navigate high-stakes organizational decisions while finding the basic bread-and-butter tasks of daily life strangely inaccessible.
You become the name everyone calls for the impossible while losing access to the curiosity and joy that made you an engineer in the first place.
I built the machine. Now the machine owns me.
I am proud of what I have built in my career.
I am also learning to be honest about what that work has consumed.
Both things can be true.
People often describe neurodiversity using the language of gifts and superpowers.
I understand why. Different forms of neurological wiring can shape remarkable abilities. Pattern recognition, hyperfocus, unconventional problem-solving, creativity, and systems thinking have all contributed to my work and my life.
But calling only the visible output a gift can erase the price paid to produce it.
People see the solution.
They do not always see the panic, sensory overload, abandoned interests, social uncertainty, executive dysfunction, anxiety, dyslexia, or the exhausting calculations happening underneath an apparently calm exterior.
They celebrate the adaptation without recognizing what required it.
That tension became “Shortcut.”
Don’t call it a gift. You never paid the price.
For many neurodivergent people, resilience is not simply strength. Sometimes it is a highly effective mask developed because failure, rejection, or being visibly different did not feel safe.
You exceed expectations because disappointing people feels dangerous.
You learn to appear composed because you perceive that the alternative will carry consequences.
Those consequences may not always be explicit or even real. But the fear of rejection, embarrassment, judgment, professional damage, or becoming a burden can still shape behavior as powerfully as a direct threat.
You become excellent at hiding the cost, and then the world uses your success as evidence that there was never a cost at all.
But adaptation and healing are not the same thing.
A person can become extraordinarily successful at concealing damage. That does not mean the damage disappeared.
Writing “Shortcut” helped me challenge the way I had learned to see myself. My abilities are real, but so is the load.
My neurodiversity is not a tragedy, but neither is it a collection of charming productivity hacks.
There was no shortcut.
There was only the long way through.
“Rootkit” began with a deliberately strange idea: dental surgery, paranoia, and the possibility that someone had implanted a listening device inside a tooth.
The dentist said I’d feel pressure. Nobody mentioned the signal.
Underneath that darkly humorous premise is something much more familiar to me: the difficulty of knowing what is real when anxiety has altered the way you interpret signals.
In computing, a rootkit embeds itself deeply in a system, gains privileged access, conceals its presence, and changes what the system can trust.
Anxiety can feel like that.
The investigator and the compromised system are the same mind.
You replay conversations. You inspect facial expressions. You analyze pauses, tone, and body language. You run packet captures on human interaction and compare versions of reality, trying to determine which interpretation is safe to believe.
Did something actually happen?
Did I invent meaning in the absence of a signal?
Was there a signal, but it was encrypted?
Did I decode it incorrectly?
Am I recognizing a real threat, or am I constructing one from static?
Sometimes it is difficult to distinguish the real from the paranoid or the unreal.
Paranoia does not always present itself as something obviously irrational. Sometimes it arrives as a plausible interpretation supported by just enough evidence to feel undeniable.
That is what makes it difficult to debug from within.
When your internal telemetry cannot be trusted, every signal becomes evidence, every silence becomes suspicious, and every missing piece invites the mind to manufacture an explanation.
You find yourself trying to “diff” reality—comparing what happened with what you remember, what was said with what may have been implied, and what you know with what your nervous system insists must be true.
“Rootkit” gave me a way to externalize that experience.
Instead of treating every anxious interpretation as either absolute truth or personal failure, I could begin examining the process producing it.
The metaphor did not make uncertainty disappear.
It did help me recognize that not every alarm is proof, not every silence contains a message, and not every signal has been decoded correctly.
Communication is not merely transmission.
A message only becomes communication when it is received and understood.
Engineers know this intuitively. Two systems can send perfectly valid signals, but without a shared protocol, no meaningful exchange occurs.
Relationships can fail in the same way.
Two people may be faithful, sincere, and deeply loving while still leaving each other feeling unseen.
One person expresses love through ordinary acts: starting the car on a cold morning, taking care of something before being asked, baking bread, or leaving a light on.
The other is listening for a different signal: touch, attention, reassurance, words that say:
I still see you.
I still choose you.
You still matter to me.
Neither person is necessarily withholding love.
But the love may not arrive in a form the other person knows how to receive.
That became “Protocol.”
You leave your love in ways I miss. I leave mine hoping you will see. Two faithful signals in the dark, and neither knows how to receive.
This was one of the most vulnerable songs for me to write because it required me to acknowledge that I have needs I do not always know how to express.
There is an especially painful loop in needing reassurance while believing that asking for reassurance invalidates it:
If I have to ask, it does not count.
But silence does not create understanding. It only leaves both people transmitting into the dark.
Writing “Protocol” helped me reconsider what connection requires.
The answer is not necessarily greater effort.
Sometimes it is translation.
Sometimes it is learning to recognize the love already being offered.
Sometimes it is being brave enough to name the signal you need.
And sometimes it means no longer relating to an outdated model of someone you love.
Do not remember only who I used to be.
Learn the version standing here now.
Identity is not a resignation letter from engineering, leadership, ambition, or dependability.
I still love complex systems.
I still enjoy solving difficult problems.
I still take pride in being someone people can rely on.
The goal is not to destroy those parts of myself.
The goal is to stop mistaking them for all of me.
The systems that helped us survive do not have to become the systems that bury us. Logic, hyperfocus, productivity, and reliability can remain valuable tools without becoming substitutes for a self.
Rebuilding identity means learning to exist when nothing is on fire.
It means recognizing needs before they become outages.
It means allowing yourself to be known before you have perfectly diagnosed what is wrong.
It means learning that uncertainty does not always require immediate resolution.
It means accepting that people cannot be reduced to root causes, dashboards, or performance indicators.
And it means occasionally letting the executive show fail so that the person underneath can finally be seen.
On August 18, I’ll release Identity: six songs about the systems we build, the roles we perform, and the person who can disappear beneath them.
The pre-release is live now on the album page—full lyrics, track notes, and audio for every song. Streaming links for Spotify, Apple Music, Amazon, and others will be added here once the album is officially released.
The tracks are:
Although these songs began with my experiences, I do not believe they belong only to me.
They are for anyone who became indispensable and then wondered whether they were still visible.
For anyone praised for resilience while quietly carrying the cost.
For anyone whose nervous system never received the message that the emergency was over.
For anyone who learned to solve every problem except the distance between themselves and the people they love.
For anyone trying to distinguish a real signal from the meaning their anxiety created in its absence.
For anyone whose life appears healthy on every dashboard while something underneath has stopped responding.
And for anyone beginning to ask:
Is the version of me that everyone knows still the real one—and am I willing to let the systems fail long enough to find out?