Week 1 · Activity that deserves a name
Define what counts as meaningful repository events in your org, and discard vanity counters.
Flagship · 6 weeks · Cohort or self-paced
Repository Pulse Analytics
Learn to build a weekly pulse that explains how work actually moves through your repositories — without turning engineers into dashboard operators.
What you will leave with
- A documented pulse covering commit throughput, review wait, merge risk, and release notes hygiene.
- Interpretation scripts for stand-ups and monthly business reviews.
- Threshold worksheets tuned with your team instead of imported benchmarks.
- A lightweight automation checklist that stays optional until week five.
Modules
Six paced weeks. Each ends with a worksheet and a short critique circle.
Week 2 · Commit flow without heroics
Chart daily and weekly commit shapes; spot freeze weeks and crunch patterns honestly.
Week 3 · Review wait as a shared cost
Measure queue time separately from review depth, then draft fair alert language.
Week 4 · Merge risk narratives
Connect large diffs, skipped tests, and late comments into stories — not blame charts.
Week 5 · Release and hotfix signals
Tag deployments so product and support can read the same pulse as engineering.
Week 6 · Publish the pulse
Ship a one-page weekly brief and a 90-day improvement backlog with owners.
Instructor
Haeun Choi
Former platform lead for a Seoul marketplace, Haeun now designs analytics curricula from the Jeju studio. She focuses on application analytics for repository activity insights that stay readable under deadline pressure.
Informational pricing
Self-paced access is listed at ₩412,000. Facilitated cohorts are ₩538,000 per seat when booked as a group of four or more. Payments are not processed on this site — use the contact form to reserve a place.
Refund policy applies to paid enrollments arranged offline.
FAQ
Do I need a specific Git host?
No. Examples use exportable CSV and API samples from common hosts. You adapt the worksheets to whatever you already pay for.
Will this replace our existing BI tool?
It will not. The course teaches interpretation and pulse design. If your BI stack is messy, we help you simplify views — we do not migrate warehouses.
What is a real limitation?
Teams with fewer than three active contributors will find some review-lag exercises thin. We note that early and suggest pairing with Contributor Heatmap Literacy instead of forcing the full flagship path.
Is Korean-language support available?
Live cohorts run in English. Office hours can include Korean clarification when scheduled in advance through the contact form.
Learner notes
“Week 3’s review-wait script cut our Slack nagging in half. I still want a clearer module on monorepos — the current examples lean toward multi-repo setups.”
“Haeun’s release tagging sheet is taped next to my monitor. Practical without being cute.”