Simpson’sparadoxspotted inthe wildModel accuracyis suspiciouslyhigh - turns outit’s justpredicting themajority classStakeholdermisinterpretsthe resultsAccidentallyduplicaterows in ajoinpipenvissueModelsdo notconvergeJeff Bezosbuys outthe LATimesDramawithFestival ofBookscodeaccidentallydeletedLAT slackchannelblows upMergeconflictViolatingstatisticalassumptionsSHAPvaluesmakesenseWeatherstoriestake overRFYLinear/logisticregressionperformedbest"test cells showconflictingresults (wins onone metric,loses on other)"Stat sigfindingStakeholderasks if wecan end atest earlyBug in testedfeaturediscoveredafter testlaunchAsk analyticsfor a metricand get agoogle sheetwith >10 tabsStat sig findinggoes awayafter correctionfor multiplecomparisonsCustomercomplainsabout StoryFinderCompletelyunintuitiveGrowthBookfunctionalityErrorloading apackageSimpson’sparadoxspotted inthe wildModel accuracyis suspiciouslyhigh - turns outit’s justpredicting themajority classStakeholdermisinterpretsthe resultsAccidentallyduplicaterows in ajoinpipenvissueModelsdo notconvergeJeff Bezosbuys outthe LATimesDramawithFestival ofBookscodeaccidentallydeletedLAT slackchannelblows upMergeconflictViolatingstatisticalassumptionsSHAPvaluesmakesenseWeatherstoriestake overRFYLinear/logisticregressionperformedbest"test cells showconflictingresults (wins onone metric,loses on other)"Stat sigfindingStakeholderasks if wecan end atest earlyBug in testedfeaturediscoveredafter testlaunchAsk analyticsfor a metricand get agoogle sheetwith >10 tabsStat sig findinggoes awayafter correctionfor multiplecomparisonsCustomercomplainsabout StoryFinderCompletelyunintuitiveGrowthBookfunctionalityErrorloading apackage

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