Most people meet my work through a live product or a write-up like this one. This is the other way in, the page that shows up when someone just searches my name. Not a resume. Closer to an answer to “so what have you actually been doing.”
Most of what's out there about me online is a resume line or a LinkedIn headline. Neither says much. I wanted one page where someone could see the actual work, and a couple of things that have nothing to do with a paycheck, so I built it into the one spot every developer already has and most leave nearly empty: their own GitHub profile.
I've built research infrastructure at Stony Brook University, medical-imaging pipelines across 50,000+ scans at Wake Forest CAIR, and production microservices serving 100,000+ monthly users at Accolite, plus billing systems handling 10,000+ daily transactions as an intern at Shriffle. I'd rather someone read that than a job title.
Ten projects, from a Chrome extension that tracks job applications to a Raft-based event log written in C++. Six get a screenshot and their real stack; four more get one line each. I'd rather someone click through and look at the code than take my word for any of it.
I keep coming back to photography, noticing light across a building or a quiet moment between people has sharpened how I think about spacing and interfaces. And near the bottom of the page there are four lines on how I actually approach the job: evidence over theatre, privacy by architecture, boring reliability, interfaces that explain themselves. Not a skills list, just what I keep coming back to.