Skip to content
DevMeme
2550 of 7590
Communication Post #2825 · source on Telegram

Drake decides post-call ratings are for judging conversation, not packet loss

Description

The meme is a two-panel Drake format over a dark grey post-call rating dialog. Top section shows a UI prompt reading “How’d the call go? Tell us about your call experience.” with three emoji-style faces (sweating sad, neutral, sparkling happy) and a checkbox label “Don’t show me this again.” Below, first yellow-tinted Drake frame has Drake turning away with palm up, and large caption to the right says “Evaluating the call from a technical point of view.” In the second frame Drake smiles and points approvingly at the camera; caption reads “Rating the conversation instead of the call itself.” The joke flips a quality-of-service survey - meant to capture jitter, latency and audio dropouts - into a subjective chat rating, highlighting how engineers often ignore intended telemetry and focus on soft-skill vibes instead

Comments

9
Anonymous ★ Top Pick 10% packet loss, jitter through the roof, Opus fell back to G.711… but the PM finally said “you were right.” That’s a five-star MOS right there
  1. Anonymous ★ Top Pick

    10% packet loss, jitter through the roof, Opus fell back to G.711… but the PM finally said “you were right.” That’s a five-star MOS right there

  2. Anonymous

    After 15 years of building distributed systems, I've learned that users will always rate their manager's rambling monologue as 'poor call quality' while a crystal-clear 4K video of a layoff announcement gets five stars for 'technical excellence.'

  3. Anonymous

    This is the engineering equivalent of asking 'How was your experience with our database?' when you really need to know if the query took 50ms or 5 seconds. When your telemetry conflates network jitter with whether Bob from accounting told a good joke, you end up optimizing for the wrong SLOs - and wondering why your perfectly stable WebRTC implementation still gets one-star reviews because someone discussed quarterly projections

  4. Anonymous

    We instrument jitter, packet loss, and MOS - yet one‑star ratings spike whenever the meeting’s about scope creep; apparently QoE measures PM entropy, not WebRTC

  5. Anonymous

    Optimizing for conversational throughput while ignoring actual commit velocity

  6. Anonymous

    When your survey asks “How’d the call go?”, you’re A/B testing Goodhart’s Law - MOS ends up measuring the sales pitch, not the WebRTC jitter buffer

  7. @V0W4N 5y

    Repost

  8. @pixelsex 5y

    someone really likes the joke huh

  9. @willowfragment 5y

    repost REEEEEEEE

Use J and K for navigation