How this course works
One week per chapter, six chapters in order. Each week describes a concrete shift in how your team operates, the principles behind it, one or more assignments to ship on your real repo, and a self-check at the end to gauge whether the week landed.
Read at your own pace. A motivated engineer can do a week in a few focused evenings; a team running it alongside day-to-day work usually wants the full calendar week. Either is fine. The point is that the practice installs into your actual workflow, not into a course portal.
No drip wall. Every week is public. Email signup below is opt-in for course updates + Bootcamp cohort announcements — not a gate.
Not an engineer? The same arc reads differently depending on your role. See the 12-week arc by role for the path through the curriculum tailored to PMs, designers, growth-ops people, tech leads, and EMs.
Tech lead or engineering manager? Once your team is internally AI-native, the bottleneck moves outside the team. The engineering-leaders supplement covers the cross-org political layer + the team-shape / hiring-filter question that the main weeks don’t address.
The six weeks
One week per chapter, in order. Each week installs a concrete shift in how the team operates — principles, assignments to ship on your real repo, and a self-check at the end. The Friday demo + weekly planning ritual gets installed end of Week 1 and runs every week thereafter.
-
Repo-as-context + the foundational triplet →
Everything for the AI, not for humans. Strategy docs, specs, decisions, planning — all in the repo as markdown, not SharePoint / Word / OneDrive / PowerPoint. Compressed planning cadence. The meeting-hygiene principle. Friday demo + weekly planning ritual launches end-of-week and runs every week after.
-
The new operating routines →
The week of installing every routine an AI-native team doesn’t do by hand anymore. Browser automation for coordination overhead. Meeting transcription pipeline. Deploy-to-prod as one skill. GitHub admin reflexive across multiple parallel branches. Environment hygiene as the substrate.
-
The 10×-everything chapter →
The single most important week. You can’t 10× engineering velocity alone — if testing, QA, monitoring, security, and DevOps don’t scale together, you bottleneck on the lowest-multiplier function and lose all the gains. Plus the framing that earns trust with engineers who feel threatened by AI.
-
Ultra-fast iteration + cross-discipline expansion →
The almost-never-say-no reflex. PR review automation. Cross-discipline scope expansion. And the honest chapter on the low-quality phase — the dip before you reach a higher final quality than slow-polish ever could.
-
Calibrated quality + the political layer →
When to polish, when to ship rough. Cross-team independence via mocks and replicas. The political conversation with managers and adjacent teams about processes that assume hand-crafted code — now with four weeks of evidence behind you.
-
Synthesis + graduation demo →
No new items. Demo one real outcome you couldn’t have shipped pre-course. Full Friday-demo + weekly-planning ritual run as the graduation exercise. Soft foreshadowing of the Fly tier (AgentHerder Bootcamp).
New lessons land roughly weekly until all six are out. Email below to be notified.
Get notified when the courses update
All six weeks are live. I’ll keep updating them as the practice evolves and as I learn from teams installing it — reworked lessons, new bonus material, new patterns surfacing from the F-Secure team, anonymised case studies from coaching. Drop your email and I’ll send a note when there’s a meaningful update or when the next live Bootcamp cohort opens.
No spam. One email per meaningful update. Unsubscribe with one click.