Showing the work without shipping the source

TODO(starr): This is a starter post. Keep it, rewrite it, or delete it — it exists to show the format and to seed the writing section.

A lot of roles ask for “a GitHub repository.” For anyone whose best work lives in a private product, a proprietary codebase, or research under embargo, that request is awkward: the strongest evidence of skill is exactly the code you can’t hand over.

This site is my answer. Instead of leading with raw source, it leads with the things that actually demonstrate senior judgment:

• The reasoning behind a system, not its source — architecture decisions, trade-offs, and what I’d do differently.
• A live product you can use, at myAevum.ai, which says more than a repository ever could.
• Writeups like this one, where the thinking is the artifact.

The repository for this site is public — so the “show me a GitHub” box gets ticked — while the work that needs to stay private stays private. The signal a good reviewer is really after is “can this person reason about hard problems and ship?” That’s answerable without a single line of proprietary code.