codeaccidentallydeletedAccidentallyduplicaterows in ajoinSimpson’sparadoxspotted inthe wildpipenvissueStat sigfindingCompletelyunintuitiveGrowthBookfunctionalityErrorloading apackageBug in testedfeaturediscoveredafter testlaunchModelsdo notconvergeViolatingstatisticalassumptionsMergeconflictModel accuracyis suspiciouslyhigh - turns outit’s justpredicting themajority classAsk analyticsfor a metricand get agoogle sheetwith >10 tabsCustomercomplainsabout StoryFinderJeff Bezosbuys outthe LATimesWeatherstoriestake overRFY"test cells showconflictingresults (wins onone metric,loses on other)"SHAPvaluesmakesenseStakeholdermisinterpretsthe resultsStakeholderasks if wecan end atest earlyLAT slackchannelblows upLinear/logisticregressionperformedbestDramawithFestival ofBooksStat sig findinggoes awayafter correctionfor multiplecomparisonscodeaccidentallydeletedAccidentallyduplicaterows in ajoinSimpson’sparadoxspotted inthe wildpipenvissueStat sigfindingCompletelyunintuitiveGrowthBookfunctionalityErrorloading apackageBug in testedfeaturediscoveredafter testlaunchModelsdo notconvergeViolatingstatisticalassumptionsMergeconflictModel accuracyis suspiciouslyhigh - turns outit’s justpredicting themajority classAsk analyticsfor a metricand get agoogle sheetwith >10 tabsCustomercomplainsabout StoryFinderJeff Bezosbuys outthe LATimesWeatherstoriestake overRFY"test cells showconflictingresults (wins onone metric,loses on other)"SHAPvaluesmakesenseStakeholdermisinterpretsthe resultsStakeholderasks if wecan end atest earlyLAT slackchannelblows upLinear/logisticregressionperformedbestDramawithFestival ofBooksStat sig findinggoes awayafter correctionfor multiplecomparisons

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