In Memory of Zach
Zach was difficult to summarize.
That would probably have pleased him.
He was a father, builder, hacker, security researcher, entrepreneur, technologist, problem solver, occasional chaos merchant, and a man who spent an extraordinary amount of his life trying to understand how things worked beneath the surface.
Systems fascinated him.
Computer systems. Organizations. Businesses. People. Security. Artificial intelligence. The strange machinery behind everyday life that most people simply accept because examining it closely sounds exhausting.
Zach examined it anyway.
His professional life refused to follow the tidy trajectory people like to put on LinkedIn. He worked across hospitality, operations, management, technical support, IT infrastructure, cybersecurity, incident response, security research, and entrepreneurship. He could move from talking about managing people and operations to dissecting an OAuth implementation, investigating a vulnerability, working through an OSINT problem, or arguing about what actually constituted evidence.
He became particularly interested in offensive security and bug bounty research. What mattered to him was not simply finding something strange and declaring victory. He cared about proving what was actually happening. He learned to distinguish an observation from an exploit, possibility from evidence, and an interesting behavior from a genuine security vulnerability.
That distinction says something larger about him.
Zach wanted to know what was actually true.
He could entertain strange possibilities, unconventional ideas, and questions other people dismissed. But when something mattered, he kept returning to evidence. Test it. Reproduce it. Challenge the assumptions. See whether the claim survives contact with reality.
Sometimes it did.
Sometimes it spectacularly did not.
Either result was useful.
In later years, artificial intelligence became another enormous intellectual playground. Zach did not see AI merely as a chatbot or productivity trick. He became interested in what happened when AI was given memory, context, tools, and a place inside the actual machinery of an organization.
That obsession eventually became part of his work on Preshift.
Preshift was more than another software project to him. It became a proving ground for an idea he called Operational Memory: the belief that organizations should be able to remember what happened, why decisions were made, what was tried, what failed, and what was learned instead of repeatedly sacrificing institutional knowledge to forgotten conversations, departed employees, and the ancient corporate tradition of nobody remembering why anything works.
He wanted to prove the idea inside his own company first.
Then take what worked elsewhere.
That was very Zach.
Build it. Break it. Learn from it. Build it again.
His curiosity was rarely confined to one subject for long. One conversation might involve penetration testing or Linux; another business strategy, AI, employment, some obscure thrift-store object, technology, history, or an idea discovered at an unreasonable hour that suddenly required investigation.
There was always another rabbit hole.
But underneath all of those interests was something considerably less technical.
Zach cared about leaving something behind.
Not merely money, a company, a vulnerability report, or a collection of projects. He wanted his life to have mattered to the people who knew him.
Above everything else, he was Ronin's father.
Life did not always make that role easy. There were periods of upheaval, financial uncertainty, relationships changing, possessions disappearing, plans collapsing, and circumstances looking nothing like the future he once imagined.
But being Ronin's dad remained part of the center of gravity of his life.
His concern was not simply whether his son would remember him.
It was what his son would remember.
Zach was imperfect, sometimes stubborn, occasionally impulsive, intensely curious, and entirely capable of turning a simple question into a multi-hour investigation.
He could be funny at exactly the wrong moment.
He could doubt himself and then, almost immediately, become convinced he'd discovered something nobody else had noticed.
Occasionally he actually had.
He could start over.
That may ultimately be one of the most important things to say about him.
There were chapters in Zach's life when starting over wasn't inspirational. It wasn't accompanied by triumphant music or some conveniently timed revelation about personal growth.
It just hurt.
And he did it anyway.
He lost things he expected to keep. He watched versions of his future disappear. He experienced the humiliating practical realities that accompany major life changes: money, housing, work, transportation, possessions, paperwork, uncertainty, and figuring out what the hell comes next.
Then he kept building.
A new idea.
A new project.
A new career possibility.
A new experiment.
A new version of himself.
Not because he possessed some magical immunity to failure, but because curiosity kept dragging him toward tomorrow.
There was still something he wanted to understand.
Something he wanted to make.
Something he wanted to prove.
And someone he loved enough to keep trying for.
If Zach leaves behind any lesson, perhaps it is that a person's life should not be measured only by the periods when everything was working.
Sometimes character is revealed much more clearly in the wreckage.
He kept asking questions.
He kept learning.
He kept making things.
He kept looking for the vulnerability everyone else had missed.
He kept trying to turn hard-earned experience into something useful.
And when life dismantled the version of himself he thought he was supposed to become, Zach did something wonderfully inconvenient.
He refused to consider the story finished.
For Ronin, there is something especially important worth preserving:
Your father was extraordinarily proud to be your dad.
Whatever else he built, discovered, attempted, lost, recovered, or left unfinished, you were never merely another entry in the story.
You were one of the reasons the story mattered.
Zach's life cannot honestly be described as neat.
It was curious, technical, funny, difficult, ambitious, occasionally ridiculous, frequently unfinished, and unmistakably his.
There were bugs.
There were failed deployments.
There were undocumented features.
There were several decisions that probably should never have reached production.
But the system kept running.
And while Zach was here, he kept trying to make the next version better.