Teaching came naturally.
Long before AI systems and production pipelines, the signal was simple. Explaining hard things clicked. The classroom instinct has stayed constant.
AI systems - learning loops - human adoption
Teaching has been the constant. I build AI systems from scratch because the inside view makes them teachable. You see where the model breaks. You see where the abstraction leaks. You see where someone is likely to get stuck.
Build the system. Then teach from inside it.
The clearest lessons come from things people can inspect, question, and change. Prototypes, experiments, and workflows reveal where real understanding gets stuck.
The through-line
Long before AI systems and production pipelines, the signal was simple. Explaining hard things clicked. The classroom instinct has stayed constant.
A Ph.D. started as a path toward teaching. It became a love of experiments. I liked the humbling work of designing something without knowing if it will hold.
Building ML models, distributed systems, and early MLOps clarified the real question. How do you make what is being built understandable enough to use?
GitHub projects
Here are a few public projects from my GitHub. They show the kinds of AI systems, teaching tools, and technical explainers I like to build.
A GPT model built from scratch in readable PyTorch. It covers BPE tokenization, causal self-attention, training, sampling, and perplexity evaluation.
Open repositoryA local, read-only analytics server where an LLM proposes typed analysis plans, validates them, and executes safe dataframe operations instead of seeing raw data.
Open repositoryA numbers-first walkthrough of residuals, similarity scores, gain, learning rate, gamma, and lambda, worked by hand and checked against the real library.
Open repositorySchovia
I create explainer videos and practical lessons that make AI concepts feel intuitive. The work is to help people understand what is happening inside the system, not just memorize the tools.
Watch Schovia videosRAG quality as an engineering pipeline, not a single vector search checkbox.
Answers have to be correct, grounded, and safe enough to use.
More tokens can help, but clean context and decision structure often matter more.
Proof, not polish
AI enablement programs for developers, product managers, and executives, with NPS 60+ and curriculum updates shipped within days of major model releases.
Technical explainers on RAG, LLM evaluation, vector search, MCP, transformers, and developer workflows.
Production ML interpretability and dataset suitability, plus additional pending work.
h-index 11, with venues spanning Genome Biology, IEEE, ICMLA, USENIX HotEdge, and SPIE.
Artifacts I care about
TinyGPT and XGBoost From Scratch turn algorithms into inspectable code, notebooks, and visual explainers instead of treating APIs as the lesson.
MCP DataFrame QA applies a research-informed pattern to local analytics. It uses compact schema context, typed plans, validation, capped outputs, and auditable execution.
Model monitoring, analytics platforms, feature workflows, interpretability, and dataset suitability systems at Parallel Machines, later acquired by DataRobot.
ML and computer vision pipelines for Harvard Medical School clinical research, including co-first-author work in Genome Biology.
Teaching experience
Expert intuition hides steps. Good teaching notices the missing step and makes it visible.
Research taste means knowing what you do not know yet, then designing a way to find out.
If the knowledge cannot update as the system changes, it is documentation theater.
Current coordinates