Learning paths
From first notebook to review-ready capstone
Members move through three measured chapters—syntax confidence, pipeline discipline, then integration studio. Each chapter ends with a mentor-reviewed artifact you can show a desk lead without apology.
Chapter A — Syntax confidence
Short drills, typed examples, and paired fixes on messy CSV edge cases. You leave with a personal snippet library and a checklist for handing work to the next shift.
Chapter B — Pipeline discipline
Logging, dry-run switches, and small tests around transforms. You practice narrating failure modes the way operational teams expect in incident threads.
Chapter C — Integration studio
Cross-cutting repo with ingestion, validation, and memo-ready visuals. Mentors grade reviewability, not flash, and capstones include an honest limitations page.
Operational Python, taught like a quiet editorial desk
- Live mentor notes on two milestones every cohort
- Notebook templates aligned to cross-org workflow language
- Office hours that stay bounded—no endless queue drama
Activity snapshot: mentor threads stay busy mid-week; new cohort channels open on Sundays; project rooms stay calmer than chat feeds.
- Scan the paths above
- Pick a course row that matches your desk
- Introduce yourself in the welcome channel
As seen in conversations
- Field Notes Asia
- Notebook Review
- Sync Weekly
- Operations Craft Record
- Desk Documentation Dispatch
- Regional Analysts Guild letter
Ambassadors
Five members model how we disagree in writing, cite notebooks precisely, and surface limitations early. They are not mascots—they moderate threads when mentors are offline.
| Member | Focus | Quote |
|---|---|---|
| Sohee Ryu | Data hygiene | “We stopped treating ‘done’ as ‘runs on my machine’.” |
| Mateo Alvarez | Pipelines | “Dry-run logs are now the first attachment in our handoffs.” |
| Yui Taneda | Visual memos | “Captions carry the decision; charts stay spare.” |
| Arjun Mehta | Activity log sync drills | “Exception exports read like emails, not puzzles.” |
| Lina Okafor | Community tone | “We reward precise questions more than fast answers.” |
Forum preview
Threads awaiting a careful reply.
How do you caption overlapping bands?
Makefile vs task runner for tiny teams
Join channels
Tabs keep the flow obvious: create your account, tell us your desk context, then land in the cohort channels matched to your course.
Use a durable email—cohort invites and mentor threads land there. Passwords must be twelve characters with mixed cases and symbols.
Tell us your desk context, timezone, and which course row you are considering. Moderators read this before routing you.
We open matched channels after verification. Lurking is fine; posting introductions helps mentors tailor examples.