Errorloading apackageStakeholdermisinterpretsthe resultsStat sig findinggoes awayafter correctionfor multiplecomparisonsModel accuracyis suspiciouslyhigh - turns outit’s justpredicting themajority classCustomercomplainsabout StoryFinderBug in testedfeaturediscoveredafter testlaunchStakeholderasks if wecan end atest early"test cells showconflictingresults (wins onone metric,loses on other)"MergeconflictWeatherstoriestake overRFYLinear/logisticregressionperformedbestJeff Bezosbuys outthe LATimespipenvissueSimpson’sparadoxspotted inthe wildAsk analyticsfor a metricand get agoogle sheetwith >10 tabsStat sigfindingModelsdo notconvergeCompletelyunintuitiveGrowthBookfunctionalitycodeaccidentallydeletedSHAPvaluesmakesenseDramawithFestival ofBooksLAT slackchannelblows upViolatingstatisticalassumptionsAccidentallyduplicaterows in ajoinErrorloading apackageStakeholdermisinterpretsthe resultsStat sig findinggoes awayafter correctionfor multiplecomparisonsModel accuracyis suspiciouslyhigh - turns outit’s justpredicting themajority classCustomercomplainsabout StoryFinderBug in testedfeaturediscoveredafter testlaunchStakeholderasks if wecan end atest early"test cells showconflictingresults (wins onone metric,loses on other)"MergeconflictWeatherstoriestake overRFYLinear/logisticregressionperformedbestJeff Bezosbuys outthe LATimespipenvissueSimpson’sparadoxspotted inthe wildAsk analyticsfor a metricand get agoogle sheetwith >10 tabsStat sigfindingModelsdo notconvergeCompletelyunintuitiveGrowthBookfunctionalitycodeaccidentallydeletedSHAPvaluesmakesenseDramawithFestival ofBooksLAT slackchannelblows upViolatingstatisticalassumptionsAccidentallyduplicaterows in ajoin

DS Bingo - Call List

(Print) Use this randomly generated list as your call list when playing the game. There is no need to say the BINGO column name. Place some kind of mark (like an X, a checkmark, a dot, tally mark, etc) on each cell as you announce it, to keep track. You can also cut out each item, place them in a bag and pull words from the bag.


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
  1. Error loading a package
  2. Stakeholder misinterprets the results
  3. Stat sig finding goes away after correction for multiple comparisons
  4. Model accuracy is suspiciously high - turns out it’s just predicting the majority class
  5. Customer complains about Story Finder
  6. Bug in tested feature discovered after test launch
  7. Stakeholder asks if we can end a test early
  8. "test cells show conflicting results (wins on one metric, loses on other)"
  9. Merge conflict
  10. Weather stories take over RFY
  11. Linear/logistic regression performed best
  12. Jeff Bezos buys out the LA Times
  13. pipenv issue
  14. Simpson’s paradox spotted in the wild
  15. Ask analytics for a metric and get a google sheet with >10 tabs
  16. Stat sig finding
  17. Models do not converge
  18. Completely unintuitive GrowthBook functionality
  19. code accidentally deleted
  20. SHAP values make sense
  21. Drama with Festival of Books
  22. LAT slack channel blows up
  23. Violating statistical assumptions
  24. Accidentally duplicate rows in a join