Skip to content
About

Curious, multi-disciplinary, and only just getting started.

I'm eighteen, a recent graduate of Albuquerque Academy, and this fall I head to the University of Michigan to study Aerospace Engineering with a minor in Business.

But the throughline of everything I do is software. It's the discipline I keep coming back to, because it's the one that lets me chase whatever I'm curious about. Curiosity about the sky turned into a pipeline that takes raw telescope frames and produces calibrated brightness measurements. Curiosity about markets turned into infrastructure for proving my own ideas wrong. Curiosity about how knowledge compounds turned into a 10,743-note architecture with semantic search over it.

I understand every line I ship. I make the architectural decisions, debug the hard problems, and can defend every design choice. Working software is the baseline. Software you can stand behind is the standard.

I'm taking on freelance work now, and I'll keep taking it on remotely once I'm in Ann Arbor. If you have something worth building, I want to hear about it.

Based

Albuquerque, New Mexico

Studying

Aerospace Engineering, minor in Business — University of Michigan

Works in

Python, TypeScript, Next.js, pandas, Astropy, ffmpeg, SQL

How I work

Four rules I don't bend.

01

Ship end-to-end

I take projects from raw idea to live deployment: design, architecture, implementation, debugging, ops, and iteration, all of it owned. Nothing gets handed off to someone else, and nothing gets left half-finished.

02

Real data only

No synthetic series, no simulated demos. Every system is tested against actual inputs: real telescope frames, real market bars, real user flows. Edge cases are where software lives or dies.

03

Validate before you trust

Backtests lie and mocks deceive. I build validation infrastructure alongside the system, then watch how it behaves under real load before claiming it works. Believing a false positive always costs more than verifying.

04

Own what ships

I understand every line of code I deliver. I make the architectural decisions, debug the failures, and can defend every design choice. If it ships under my name, I can explain exactly how it works.

So far
  1. 2026

    Graduated Albuquerque Academy

    Twelve years in one place, which turns out to be long enough to learn how you learn.

  2. 2026

    Built the validation framework

    Nineteen strategies tested against seven years of out-of-sample data. Eighteen shelved, one short of data, none deployed — which was the point. The framework existed to find that out rather than to confirm what I hoped.

  3. 2026

    QuantVault reached 10,743 notes

    Eight domains with semantic retrieval across the whole corpus. Built like software because a pile of notes without architecture is write-only.

  4. Fall 2026

    University of Michigan

    Aerospace Engineering, minor in Business, Ann Arbor.