A pattern-minded builder with a long memory for hard problems.

The explorer was there before the résumé.

As a kid, I was the one leading other kids into the hills. Around age ten, I organized small expeditions that turned into miles of hiking, fossil beds, hidden structures, and abandoned tunnels. I was not chasing attention. I wanted to know what was around the next ridge, how things connected, and what everyone else had missed.

Fatherhood changed the scale of what matters.

I am a single dad to a four-year-old daughter who has already lived through three open-heart surgeries. That experience changed me. It made patience less theoretical, priorities less negotiable, and resilience much more practical.

It also changed how I work. I have less tolerance for wasted motion and more respect for care, precision, preparation, and people who quietly do the hard thing well.

The right conversation is about the hardest problems solved.

I respect credentials, but I do not worship them. The better signal is evidence: what did you build, what made it hard, what tradeoffs did you make, and what survived contact with reality?

That is the kind of conversation I want with serious builders. Not a pile of buzzwords. Not borrowed prestige. The work itself: cached Azure operations, agentic Article Studio workflows, edge model routing, telemetry, and product experiences that survive real iteration.

A second-act education, not a straight-line credential story.

I went to community college at 28, then found my way to U.C. Berkeley and later UNR. That path matters because it was earned later, deliberately, while building a life and a career rather than following a perfectly timed script.

I am drawn to people who keep learning after the easy window has closed. That kind of learning tends to be more durable. You know exactly why you are there.

I am not driven by ego. I am driven by the build.

I like knowledge sharing, camaraderie, and the feeling of a serious team solving something together. I like the person who notices the quiet bug. I like the teammate who documents the thing nobody wanted to document. I like the founder who wants the truth more than applause.

My personality is direct, curious, and a little stubborn in the useful way. I want the system to work. I want the explanation to be clean. I want the next person to have a better map than I had.