Notes from people who sat through a review
These are accounts of particular screens, SIMs, and arguments — not a star widget. One of them still wishes we had been slower to call a crash “won’t fix.”
Short notes
“They timed our grocery cart on the Ampang LRT with a Maxis SIM. Office Wi-Fi had hidden a promotions call that had no timeout. We shipped the listing two days late and kept the timeout. I still think they were harsh on the splash animation; shoppers never mentioned it.”
— Siti Hajar, product owner, Petaling Jaya grocer
“The crash walkthrough forced us to stop treating a map library as the villain. The cluster sat on the checkout button after a failed 3D-secure return. Half the room wanted to ignore it because it was ‘only 0.8 percent.’ We did not ignore it.”
— Daniel Khoo, engineering lead, Penang payments team
“Battery review after our Raya blast showed the radio waking every four minutes for a receipt sync nobody had turned off. The note was six pages. I wanted a one-pager for the CEO; Priya refused to flatten the commute numbers.”
— Meera Chandran, growth, fashion listing on both stores
A longer afternoon: ticket gates in Shah Alam
Farid Hassan’s stadium app had passed internal QA on fibre. On event day the gate screen drew a spinner for nine seconds after the QR was shown. We froze a build on a Thursday, walked the same underground corridor the ushers use, and recorded the spinner against a Celcom SIM that dropped to a constrained radio.
The findings note did not invent a new architecture. It named the certificate pin retry and the lack of a cached pass. Farid’s team shipped a fallback the following week. He later said the workshop felt “abrupt” — we stopped when the trace ended, and he had hoped for a longer design conversation. That conversation belongs to his designers; we still will not pad a note to fill ninety minutes.
If a similar freeze week would help, request a release review.