Flagship programme
Production Crash Analytics: From Signal to Ship Decision
Eighteen hours across six live sessions and a release-gate studio. You leave with a clustering rubric, a symbolication checklist, and a one-page stability brief designed for launch review — not for a wiki that nobody opens.
Learning outcomes
- Separate vendor “same crash” labels from a grouping you can defend.
- Spot session-rate swings caused by traffic mix, not by a new binary.
- Write a hold/ship condition that names a user journey and a reopen rule.
- Run a 36-hour symbolication freeze before declaring a P0 on a new release.
- Brief a product manager without dumping a stack trace into Slack.
Instructor
Nalinee Thongchai
Former reliability lead on a regional super-app. She still reads anonymised production exports the night before each cohort and will cancel a lab if the dump is mostly server errors.
Modules
-
How your feed currently lies
Map the vendor UI you already pay for. We mark fields that look like quality but actually track volume, geography, or OS mix. Homework: bring one screenshot you no longer trust.
-
Clustering without erasing users
Heuristics for splitting “identical” stacks when the failing line is shared infrastructure. Lab on a redacted Android export from a prior Bangkok cohort.
-
Symbolication as a clock, not a chore
dSYMs, mapping files, and the 36-hour rule. Why a “new” crash on release day is often an old crash wearing an unsymbolicated face.
-
ANR and freeze adjacent to crash
Enough Android vitals literacy to stop treating every ANR as a crash cousin. Full ANR desk is a separate programme; this module is the boundary.
-
Release-gate dashboard
Build the one-pager: three clusters, owners, hold condition, reopen condition. PMs join this session when possible.
-
Studio critique
Pairs present a gate for a fictional payday weekend in Thailand. Faculty argue. You revise once. That artefact is what we consider “completion,” not attendance.
Informational fee
฿24,800 per public-cohort seat. Bench Seat recordings are listed on pricing at ฿19,400. Release Room (up to eight people, flagship plus ANR) is ฿86,000. No payment is taken on this website.
Seats include session recordings for 90 days and the alumni mailing list. Vendor licences are yours to buy.
Ask about the next cohort
FAQ
Do I need a specific crash vendor?
No. Labs use redacted exports that resemble the major mobile vendors. You should already be collecting crashes; we do not teach SDK installation from zero.
What does this programme refuse to cover?
This programme does not cover backend error budgets or web RUM. If your “crashes” are mostly server-side 500s, the labs will feel misaligned. We will say so on the first call rather than stretch the syllabus.
Can product managers attend without reading stacks?
Yes for module five and the studio. The first four sessions still expect an engineering partner in the pair. The PM-only desk is Stability SLOs.
Is there a certificate?
We send a letter confirming you completed the studio artefact. We do not sell framed certificates or LinkedIn badges.
From people who sat this syllabus
The release-gate module is the reason we still mention Devqueuegrid in launch review. Clustering week was slower than I wanted; Nalinee would not let us skip the boring symbolication clock.
★★★★☆
Flagship, October 2025. Useful, slightly Bangkok-centric on festival traffic examples. Remote audio was fine. I wanted more iOS time; that lives in Arthit’s separate desk.