Blog
Why we rehearse gateway brownouts before teaching MQTT
2025-11-18 · Evelyn Cho
We used to start MQTT labs on pristine networks. Learners passed locally, then blamed “weird production” when duplicate client IDs surfaced weeks later. That mismatch felt dishonest, so we flipped the order: brownout rehearsal first, broker semantics second.
The rehearsal is a tabletop plus simulator script. Pairs rotate through facilitator, scribe, and operator roles so nobody hides behind a single hero engineer. We log decisions on a shared sheet that intentionally omits vanity metrics—only states, timestamps, and human verbs.
When MQTT finally arrives, participants already know how duplicated publishes feel in the activity log. They ask sharper questions about QoS choices because they have tasted the failure mode instead of memorizing acronyms.
If you join a cohort remotely, you still get the same script; we ship a printed timeline so you can run the exercise with sticky notes on a kitchen table. The goal is shared vocabulary, not identical lab benches.