Week 62 — Online evaluation

ML lifecycle, experimentation, and MLOps · Read / diagram

Medium

Phase 6 — ML lifecycle, experimentation, and MLOps

Overview

A/B tests, shadow deployment, canary, bandits

Mode this week: read_diagram. Match the work to that mode (operating model): implement ships running code; read/diagram ships a doc; deploy/benchmark ships a measured run. Personal dates, checkboxes, and the RPG layer stay in a learner journal.

Core deliverable

Rollout plan

Optional depth

Add a benchmark, failure-mode analysis, and a short production trade-off note.

Week loop (from the cookiecutter journal)

Mon — Theory: A/B tests, shadow deployment, canary, bandits
Tue — Build: start the core deliverable above
Wed — Systems / papers: one paper or system note (see below if this week has assigned reading)
Thu — Eval / interview: write the four evidence items
Fri — Algorithmic Forge: Evaluation or assignment tool with algorithmic analysis (45-90 min; Core)

Forge theme: DP, greedy, bitmask DP, probability DP, experiment assignment

Leetcode Darbar (parallel)

This week's band (58-69): Dynamic programming, greedy, math, probability. Production connection: Experiment assignment, rollouts, monitoring.

Standard: one aligned problem. Auror: the five-slot queue on the Darbar page. Tracker stays in the learner journal.

Topics: dynamic programming · greedy · math

Fibonacci Number · easy · dynamic programming
Longest Palindrome · easy · greedy
Divisor Game · easy · math

Evidence contract

Every core week records all four (cookiecutter journal/weeks/week_062.md):

Code / implementation (or the design artifact on a writing week)
Benchmark / result
Design doc / technical explanation
Retrospective / learning note (Sailboat: destination, wind, anchor, rocks, heading)

On this site

Official Tensor-to-Tenant

Week 62 of Tensor-to-Tenant · Previous week · Next week.