Week 30 — Statistics IV

Mathematical foundations II: calculus, autodiff, probability, statistics · Implement

Easy

Phase 3 — Mathematical foundations II: calculus, autodiff, probability, statistics

Overview

Power, MDE, sample size, multiple testing

Mode this week: implement. 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

Experiment-size calculator

• Gate 3 this week: Derive basic gradients; explain MLE/MAP; implement hypothesis tests + bootstrap CIs; explain power/MDE

Optional depth

Package the strongest work from this program as a portfolio release with a benchmark, explanation, and retrospective.

Week loop (from the cookiecutter journal)

• Mon — Theory: Power, MDE, sample size, multiple testing
• 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: Expectation DP, combinatorics, modular arithmetic, and one optimization search problem. (2-3 hr; Boss fight)

Forge theme: Week 30 - Foundations mini-contest

Leetcode Darbar (parallel)

This week's band (7-30): Math, bit manipulation, divide and conquer, recursion, backtracking. Production connection: Linear algebra, probability, statistics, optimization.

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

Topics: backtracking · bit manipulation · divide and conquer · math · recursion

• Binary Tree Paths · easy · backtracking
• Count Number Of Maximum Bitwise Or Subsets · medium · bit manipulation
• Convert Sorted Array To Binary Search Tree · easy · divide and conquer
• Divisor Game · easy · math
• Reverse String · easy · recursion

Evidence contract

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

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

On this site

• Hypothesis testing
• Confidence intervals
• Bootstrap mean
• KL divergence

Official Tensor-to-Tenant

• Curriculum browser
• Milestone gates
• Weekly operating model
• Leetcode Darbar
• 36-week on-ramp
• Source repo

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