A small faculty that still sits with production exports.

Mission

We exist so that crash and stability analytics become a shared language between engineering, product, and store operations. A crash feed that only engineers can decode will always lose to a launch date. Our job is to make the feed readable without sanding off the technical truth.

Pedagogy

Every programme follows the same rhythm: a short briefing, a lab on a real export, a critique, then a one-page artefact you can take into your next release review. We refuse slide-only days. If a concept cannot be practised on a stack trace, a vitals chart, or a sampling config, it does not belong in the timetable.

Students work in pairs across companies when possible. A fintech Android lead reading a ride-hailing ANR is often more honest than a teammate who already knows the political story behind the bug.

Community

Alumni stay on a quiet mailing list. We send a monthly desk note, not a newsletter of product launches. Twice a year we host an evening in the Bangkok studio for people who want to bring a thorny cluster. Attendance is optional and uncapped by “level.”

Student journey

Most people arrive after a bad store week: a crash-free dip, a Play vitals warning, or a PM who has started screenshotting dashboards into Slack. Week one is diagnosis of how you currently read telemetry. Mid-programme you build a clustering rubric and a release gate. After the last session we ask for one production change within fourteen days — not a tool migration, a decision habit.

Thailand’s consumer apps often see traffic spikes around festivals and payday cycles that US-centric playbooks ignore. We keep those calendars on the wall. If your users are primarily in SEA, you will recognise the examples; if they are not, you will still recognise the method.