Stakeholderasks if wecan end atest earlypipenvissueStat sigfindingDramawithFestival ofBooksStakeholdermisinterpretsthe resultsMergeconflictCompletelyunintuitiveGrowthBookfunctionalityWeatherstoriestake overRFYModel accuracyis suspiciouslyhigh - turns outit’s justpredicting themajority classcodeaccidentallydeletedLAT slackchannelblows upJeff Bezosbuys outthe LATimesAsk analyticsfor a metricand get agoogle sheetwith >10 tabsBug in testedfeaturediscoveredafter testlaunchSimpson’sparadoxspotted inthe wildAccidentallyduplicaterows in ajoinCustomercomplainsabout StoryFinderStat sig findinggoes awayafter correctionfor multiplecomparisonsModelsdo notconvergeViolatingstatisticalassumptionsErrorloading apackageSHAPvaluesmakesense"test cells showconflictingresults (wins onone metric,loses on other)"Linear/logisticregressionperformedbestStakeholderasks if wecan end atest earlypipenvissueStat sigfindingDramawithFestival ofBooksStakeholdermisinterpretsthe resultsMergeconflictCompletelyunintuitiveGrowthBookfunctionalityWeatherstoriestake overRFYModel accuracyis suspiciouslyhigh - turns outit’s justpredicting themajority classcodeaccidentallydeletedLAT slackchannelblows upJeff Bezosbuys outthe LATimesAsk analyticsfor a metricand get agoogle sheetwith >10 tabsBug in testedfeaturediscoveredafter testlaunchSimpson’sparadoxspotted inthe wildAccidentallyduplicaterows in ajoinCustomercomplainsabout StoryFinderStat sig findinggoes awayafter correctionfor multiplecomparisonsModelsdo notconvergeViolatingstatisticalassumptionsErrorloading apackageSHAPvaluesmakesense"test cells showconflictingresults (wins onone metric,loses on other)"Linear/logisticregressionperformedbest

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