About the studio

We teach the unglamorous layer that makes product analytics trustworthy.

Socket Nodehub began as a Friday review table for Bangkok product teams who were tired of rebuilding funnels after every app release. The table became a studio. The studio still sits on Charoennakorn.

Mission

In-app event tracking analytics should be a shared language, not a private dialect inside one analytics tool. We train people to write that language so marketing, engineering, and data can argue about meaning instead of missing rows.

We are not a vendor academy. Students leave able to move a dictionary between Amplitude, Mixpanel, a CDP, or a warehouse without rewriting the product’s history.

Bright office interior with long communal tables

Pedagogy

Bring a live dictionary

Every studio seat starts with the student’s actual event list, even if it is a spreadsheet with duplicate click events. Hypothetical apps are reserved for Atlas Reader only.

Clinic before lecture

We read payloads first. Theory arrives after the room has seen a property that cannot be joined. People remember the join failure longer than a slide.

Public critique, private data

Schemas are reviewed in class with names stripped. Identity examples stay synthetic unless a student explicitly opts a redacted excerpt in.

Adult learners in a small classroom

Community

Alumni keep a quiet channel for dictionary reviews. It is not a social network. People post a property they are unsure about, and someone who sat the same module answers with a yes, a no, or a “needs a version field.”

Once a quarter we host an evening in Bangkok for local alumni and visiting remote students. The river is nearby; the conversation is still about nulls and late events.

Student journey

01

Application note

Tell us which app surface hurts: checkout, onboarding, or a feature flag that never quite attributes. We reply within two working days.

02

Placement read

Atlas Reader, Studio, or House Account. If your team already has a governance lead, we often skip Atlas and go straight to clinic weeks.

03

Schema draft

You leave week three with a named object list and forbidden vanity events. Engineering can implement while later weeks cover identity and warehouse types.

04

Review and handoff

The last session is a critique, not a certificate ceremony. You leave with a versioned dictionary and a QA checklist written for the people who ship the app in Thailand or elsewhere.