Rule #3: Code or Die

Code as leverage rather than as a career: the discipline that converted survival intelligence into agency and exits.

Code or die is not a slogan about software supremacy. It is a statement about leverage.

For me, code was never just an employable skill. It was one of the first disciplines that let me convert intelligence into mobility at scale. It gave me structure when my inner life was chaotic. It gave me feedback that was hard but legible. It gave me a way to build value in environments that might otherwise only see a former foster youth with too much intensity and a complicated story.

Code gave me a weapon that did not require me to become less myself.

That matters.

A lot of systems will let you rise only if you agree to become digestible first. Code did not ask for digestibility. It asked for rigor. Attention. Curiosity. Persistence. Pattern recognition. All things I had in abundance, even when the rest of my life was unstable. Programming rewarded the part of me that could sit in complexity, break it down, and refuse surrender. It turned my survival brain into something generative.

That is why I say it saved my life.

Not because it made me rich overnight. Not because it solved trauma. Not because typing on a machine is inherently noble.

It saved my life because it gave me a disciplined path out of helplessness.

Helplessness is deadly. Sometimes materially. Sometimes spiritually. Sometimes intellectually. Once a person starts believing they have no meaningful leverage over their environment, the world begins shrinking around them. Code interrupted that shrinking. Every time I learned a new concept, fixed a bug, built a feature, or understood a system more deeply, I was rehearsing agency. I was reminding myself that opaque things can be studied. Hard things can be debugged. New things can be built by people who were never formally invited into the room.

That is not just technical training. That is worldview.

It is also rebellion.

When you come out of systems that mostly prepare you to be managed, learning how to build software is radical. It moves you from object to author. From case to creator. From recipient to architect. It does not erase all the structural realities around you, but it changes your relationship to them. Suddenly you are not only navigating existing systems. You are understanding how systems are made.

That is a dangerous education in the best sense.

Because once you know systems are made, you stop worshipping them. You start asking who designed this. Who benefits from this. What assumptions are baked in. What breaks at scale. Who gets left out. What could be rebuilt differently.

That way of thinking shaped much more than my career. It shaped my ethics, my leadership, and my imagination for what I owe the next kid trying to find a lever in a world built to press down on him.

And yes, I have seen code save other people too.

Not in the cheesy bootstrap fantasy where everybody learns JavaScript and all social problems vanish. I mean I have seen people become less trapped because a technical skill gave them options. Income options. Geographic options. Confidence options. Community options. Narrative options. Once a person knows how to build something valuable, the world loses some of its power to define them as passive.

That is why I care so much about teaching.

I do not teach code because I think everyone needs to become a programmer. I teach it because code is one of the clearest examples I know of disciplined learning becoming structural power. It is proof that the mind can be trained into leverage. It is proof that curiosity can become currency without becoming fake. It is proof that people society has underestimated can master abstract systems and use them to change material conditions.

Of course code has limits. I am not naive about that.

Programming cannot love you back. It cannot hold you while you grieve. It cannot replace therapy, friendship, or community. It can become obsession, escape, ego, class insulation, or another way to avoid the wound.

I know all that.

But I also know what it gave me when I needed it most: a craft sturdy enough to meet my intensity without collapsing under it.

That is rare.

Code did not ask me to be smaller. It asked me to be sharper. It did not ask me to perform innocence. It asked me to learn. It did not ask me to explain why I mattered. It let me build things that demonstrated value in real time.

So when I say code or die, I am really naming a principle:

Find the discipline that turns your mind into leverage. Find the skill that lets you build exits. Find the craft that gives structure to the part of you that might otherwise become chaos.

For me, that craft was code. And I will always treat that as sacred.