AI-Native Delivery
Teams adopting AI-assisted engineering who want the throughput gain to survive contact with review and production.
Length
5 weeks, part-time
Commitment
~5 hours per week
Cohort
12 live sessions, 20 seats
What this track assumes
Working engineering team with a live codebase.
What you cover
6 modules
Each one is worked through live, then built on between sessions.
- 01The transaction-cost argument — why generation getting cheap moves the constraint
- 02Building verification capacity — trusted suites, fast pipelines, small changes
- 03Review practice when the author did not type it — intent, invariants, accountability
- 04AI in the pipeline — migration, test generation, triage, and which uses are traps
- 05Provenance and governance — what a regulated estate has to be able to evidence
- 06Re-baselining — measuring and reporting when throughput shifts under you
You build it, then you defend it.
There is no exam and no pass for attendance. Some people do not pass first time.
The project
A before-and-after flow and quality baseline for your own team, with a written analysis of where the constraint actually moved and what you did about it.
Read first
Some of this is free
The knowledge library covers a good deal of the same ground. Start there, and pay us only once you have decided the reviewed version is worth it.
Code Review When Code Is Cheap
Review practice under high change volume. What a reviewer should look for when the author did not type the code, why pull request size discipline matters more than before, and who owns a defect nobody wrote by hand.
Forecasting When Throughput Changes
Historical throughput predicts the future only while the system is stable. What to do when capability is shifting under you — re-baselining, estimation practice, which DORA and flow metrics survive, and how to report it upward honestly.
Putting AI In The Delivery Pipeline
Where assistants belong in the lifecycle beyond code completion — test generation, large-scale migration, decision capture, triage, review assistance — which of these pay back immediately, which are traps, and what provenance a regulated estate has to evidence.
Running A Fleet Of Coding Agents
Several coding agents working a codebase in parallel. Decomposition so they do not collide, worktree isolation, why review capacity becomes the ceiling almost immediately, and the failure modes that are easy to miss.
Other tracks
The rest of the technical family
AI Foundations
6 weeks, part-time
People who already use these tools daily and want to build with them — analysts, product people, and engineers early in their careers.
AI Engineering
8 weeks, part-time
Engineers building LLM applications, retrieval systems and agents who need them to hold up in production.
Agentic Systems Engineering
7 weeks, part-time
Engineers building systems that act on their own, and the leads accountable for what those systems do unsupervised.
Physical AI
7 weeks, part-time
Engineers moving from software-only AI to systems that act in the world, where being confidently wrong has consequences you cannot undo.
Web3 & Smart Contract Security
10 weeks, part-time
Engineers moving into contract development, and teams preparing a protocol for audit and mainnet.
Mobile Delivery
5 weeks, part-time
Mobile teams whose release cadence is set by store review rather than by their own decisions.
Take AI-Native Delivery.
6 weeks, 12 live sessions, 20 seats, priced by region from $450. Places in the first cohorts are arranged directly.