Applied · notebook to product

ML in production & MLOps

Getting a model out of the notebook and keeping it honest afterwards: export, inference inside a .NET product, pipelines, tracking and monitoring.

data train evaluate export serve monitor notebook → product
  • ONNX / ONNX Runtime Production Real-time inference inside a .NET application
  • Azure ML · MLflow Applied (2026) Parallel training, champion/challenger selection
  • gRPC · protobuf · Python packaging Production One parser shared by C# and Python
  • Docker Applied Azure ML environments, teaching material
  • FastAPI · Flask Production and prototype Device services in the lab
  • LLM APIs, agents, RAG Exploring (2026) Self-directed tools and teaching material

The gap between a good notebook and a good feature is mostly unglamorous: preprocessing that matches training exactly, latency measured where the model actually runs, constants that can't drift, and a record of why each number is what it is. I have learned most of that the hard way, starting with a model that ran in real time and gave the wrong answer.

Where it shows up