★★★★☆
The PromptPay hop module saved us from shipping a “paid” event that fired on intent. I still think critique week is a day too short if your engineer is in another timezone.
Flagship · 6 weeks
A working desk for product and data pairs who need to trust a live stream. You leave with a signed naming ledger, a sampling note that states its bias, and one instrumented Thai checkout path — not a slide deck about “real-time.”
You bring the worst event name on your board. We rebuild a ledger with aliases, owners, and a kill date for deprecated keys. Homework is a one-page diff your engineer can actually merge.
We take a public-style marketplace stream and apply three sampling strategies. You compute bias on add-to-cart versus paid. The worksheet is unkind on purpose.
A live wall can be “wrong” because the consumer is behind, the producer retried, or BigQuery has not landed. This module is mostly diagnosis, not architecture.
One recorded rider session from a Bangkok evening peak. You pause, annotate drop-offs, and only then compare to the aggregate chip. Most pairs discover they were arguing about two different minutes.
You draft page-level mute rules and a “do not page for warehouse lateness” clause. We review them as if we were on-call at 01:00.
PromptPay, COD, and a dual-wallet hop. You instrument the path, state what the live board cannot see, and write the limitation into the README — not a footnote after launch.
Nalinee spent nine years leading instrumentation for a Bangkok logistics platform before opening this studio. She still keeps a paper naming ledger. She will not teach you to stand up Kafka; she will tell you when your socket consumer is flattering the conversion rate.
The Live Usage Lab is listed at ฿18,500 per seat. That covers six taught evenings, critique week, and access to the sample marketplace traces. It does not include travel, a laptop, or a production socket cluster. This page does not take payment. If you want a seat, write to the desk; invoices are issued separately under Thailand tax rules.
No. That is a real limitation, not a humble-brag. The lab is literacy for product and data pairs. We read sockets, sampling, and lag. We do not provision brokers, write consumer groups from scratch, or certify you on any vendor. If your team has nobody who can keep a consumer alive, hire that person first, then sit the lab.
Enough to join an events table to a users table and not panic. We will not spend evenings on window functions. Live boards in the lab use a thin query layer; the hard part is the meaning of the row, not the syntax.
Pairs work best: one person who owns the funnel, one who owns the pipe. A full squad tends to turn the film-strip evening into a status meeting. Floor Cohort exists if you want eight seats with a shared ledger.
A letter confirming attendance and the title of your critique piece, if you finish it. No badge marketplace. Hiring managers in Bangkok who know us ask for the ledger, not the PDF.
★★★★☆
The PromptPay hop module saved us from shipping a “paid” event that fired on intent. I still think critique week is a day too short if your engineer is in another timezone.
Came for sampling, stayed for the mute-rule worksheet. Our on-call volume dropped because we stopped paging on warehouse delay. Naming homework was tedious and correct.
“Film strip, then aggregate. I say it in stand-up now and people roll their eyes, which means it landed.”
Tell us which live path you want to bring. We reply within two working days from Pomprab.