Local-first AI developer tooling
Exploring how local models can be discovered, attached to developer workflows and exposed through a Copilot-like extension experience — with GPU/SSH execution as a deployment layer.
This page is deliberately more dynamic than a résumé. It shows the current engineering loop: experiments, active repositories and public activity.
Exploring how local models can be discovered, attached to developer workflows and exposed through a Copilot-like extension experience — with GPU/SSH execution as a deployment layer.
Building the foundations that make later transformer, fine-tuning, inference and evaluation work understandable rather than magical.
Loading live activity…
Define what the system must make possible before selecting a model, framework or API.
Prefer a small end-to-end path over a pile of disconnected notebooks.
Logs, traces, benchmarks and reproducible experiments turn “it doesn’t work” into an engineering problem.
The goal is not just code that runs — it is code whose decisions can be defended in an interview or production review.
Deploy, expose, test and iterate. The portfolio should show evidence of shipping, not only screenshots.