The strongest code evidence is often code you do not control.
A local repository can define its own success conditions. Upstream work has to survive another project's API contracts, reviewers, tests, compatibility constraints, and downstream users.
Portfolio projects are valuable but self-authored evidence. I wanted a second evidence class: small correctness fixes accepted into mature codebases whose standards I did not set.
Eight selected patches merged across MatGL, MLX-LM, Alloy, and uutils, spanning autograd, uncertainty infrastructure, inference defaults, recursive type semantics, and date/time compatibility.
Each result is a merged third-party pull request with its own review history, CI, tests, and maintainers. The links below are the proof; this page is only an index.
Merge is evidence that the change met that project's acceptance bar. It is not evidence that every design choice was optimal, nor that the patch had large product impact.
Selected merged work
What I learned
The unit of correctness gets larger upstream. The question stops being “does my example work?” and becomes “what may every downstream caller safely assume after this lands?” That shift is why the patches cluster around edge semantics: gradients, default composition, recursive representations, timezones, and compatibility behavior.