Moving in Silence Was Phase One

I posted this on January 12th, 2025.

Sixteen months later, I'm deliberately doing the opposite. Both halves belong to the same story.

I've never been the type to broadcast my shit publicly. But I don't dodge it when people ask. So here's the full answer to everyone who saw that post and probably assumed it was about drama and toxic people.

It wasn't. Or, it wasn't only that.

The real thing I was disappearing from was 16 years of my own destruction. The person I needed to protect that energy from was me.

So why talk now?

Because I have a daughter named Kinsley. And if I hadn't gotten it together, actually gotten it together, she would be growing up without me. Raised by someone else. Knowing her dad as the cautionary tale instead of the person who shows up every Friday at 3:25. That was the line. Not rock bottom. I'd had four of those. The line was Kinsley.

What I never posted

I had one hell of a detour. Whether that's fate or catastrophically bad luck followed by the most improbable survival rate, I honestly don't know anymore. What I do know is that I made bad choices, the kind that compound. Sixteen years of heavy drug abuse. Heroin. Cocaine. Xanax, anything to dull the pain and quiet the cycle. Homelessness at one point. Three, maybe four overdoses.

The last one came with a TBI I still account for every single day.

Waking up and not remembering how to use a telephone is god damn terrifying. There's a version where I only remember the cops cracking my ribs trying to bring me back from the dead. Another where I woke up in the hospital in my own piss because, as the doctor put it, "your brain was already shutting down trying to preserve what brain function was left."

I don't know how many minutes that window was. But I lived through it in real time.

The people around me had been fighting for me for years. And you can hear it when hope drains. Voices getting quieter. The exhaustion of loving someone who keeps choosing destruction. That sound is what made change non-negotiable. It had to be now, not when I felt ready. Because there were only so many attempts left before those voices stopped altogether.

What I built since waking up in that hospital bed

After a ri-fucking-diculous number of attempts, something like 7 years, I'm not proud of the timeline, I finished my associate's degree.

Then AI happened.

I jumped on it like everyone else does at first. The "how do I get rich quick" angle, the same way every person and company tries to capitalize on world-changing technology before they understand what it actually is. The internet. Mobile. Crypto. Same pattern.

Except I couldn't stop.

I got completely absorbed by a technology that let me bypass the traditional gatekeeping of software engineering. I didn't need a CS degree. I needed to understand how to architect systems. How to diagnose what a workflow was missing. How to read a process the same way I used to read a room behind a bar.

That last part turned out to matter more than I expected.

I built a website. Then another. Tested 30 tools, then 70, then over 100, absorbed what worked, discarded what didn't. Started vibe coding apps thinking I was hacking the system, only to discover how many unknown unknowns I was generating. This wasn't a shortcut. This was the thing I'm actually built for.

I work in managed IT services by day. My employer doesn't offer AI enablement, which means every business conversation I have about what AI could do for their operations is open water, and it doesn't conflict with the work that pays my bills. What it does mean: I've been operating at the intersection of enterprise IT and AI implementation, in production, with real constraints, for over a year.

Sit with that for a second. The guy who took 7 years to finish a two-year degree is teaching people with four-year computer science degrees how to architect AI systems. The credential system is a proxy for competence. I built the real thing directly.

The part I had to sit with before I could write it

The TBI didn't just almost kill me. It permanently damaged my recall memory. I had that evaluated, formally, clinically, with brain scans.

What that meant practically: I had to build systems to compensate. Obsessive documentation. External scaffolding. Automation for everything my brain couldn't hold onto. I didn't have the option of winging it. My brain couldn't be trusted, so I built infrastructure that didn't require trusting it.

The same injury that should have ended everything is the direct reason I became good at building systems that work around an unreliable mind.

I didn't recover from the damage. I engineered around it. The systems are what's holding everything up. But they work.

The part that still catches me off guard: the methodology I built to survive my own broken brain turns out to be exactly what businesses need when they're trying to implement AI without falling apart. I didn't design it that way. I just solved the problem in front of me, the same way I always have.

Why I'm posting this now

That January post said "I move in silence."

Sixteen months later I'm building in public. I read that as finishing the promise. Moving in silence was the construction phase. This is what comes after.

Some of the most interesting companies being built right now weren't built in boardrooms. They were built in public, documented in real time, by people who solved their own problems first and then realized others had the same ones. That's the model. That's what this is.

I'm ready to bring people along. People who've rebuilt. People who are in the middle of it. People who think they can't, but might surprise themselves if they stopped trying to return to who they were and started building something new instead.

The person I was can't come back. That's not the goal.

The goal is the person I'm building, and it turns out he's more functional, more resilient, and considerably better at reading systems than version 1.0 ever was.

If you've been wondering what I've been up to since that post: this. All of this.

And I'm just getting started.