9. Thebusinessneed has…evolved31. Wait…which celldid I runlast?7. Thisshould besimple,right?23. Datasethas 47samples.Total.34. Thisnotebookis 2000cells long28. Losswent toNaN onstep 1Free!40.Internetdied atdemo time15.Someonehogged allGPUs6.Stakeholderghostedafter week 216. OOMkilled atepoch 99of 1008. Just addONE morefeaturebeforelaunch19. Serverrebootedovernight.RIP myresults.30. Forgotto shufflethedataset14. Theserver issuspiciouslyslow today24. Thedata is toonoisy touse22. Whoannotatedthis?!2. Actually,let’s pivotthe entireapproach32. Jupyterkernel diedmysteriously35. As permy lastemail…36. “Quick5-minsync” = 45minutes5. Can wemake itreal-time?17. Forgotto kill myprocess…sorry team!29. Worksperfectlyon mymachine27. Groundtruth isn’tactuallytrue33.Restartkernel, runall, pray13. CUDAout ofmemory1. Can weget 99.9%accuracy?4.Requirementschanged…again10. Whenwill themodel beproduction-ready?20. Weneedmore data3. A meetingcould havebeen anemail26. Testdataleaked intotraining set18. SSHconnectiondied mid-experiment21. Thelabels arecompletelywrong38. Nicepajamatop on thecall12. Servercrashedduring thelive demo25. Extremeclassimbalancestrikes again37. I’lldocumentthis later11. Who lefttrainingrunning ALLweekend?39. Petphotobombedthe video call9. Thebusinessneed has…evolved31. Wait…which celldid I runlast?7. Thisshould besimple,right?23. Datasethas 47samples.Total.34. Thisnotebookis 2000cells long28. Losswent toNaN onstep 1Free!40.Internetdied atdemo time15.Someonehogged allGPUs6.Stakeholderghostedafter week 216. OOMkilled atepoch 99of 1008. Just addONE morefeaturebeforelaunch19. Serverrebootedovernight.RIP myresults.30. Forgotto shufflethedataset14. Theserver issuspiciouslyslow today24. Thedata is toonoisy touse22. Whoannotatedthis?!2. Actually,let’s pivotthe entireapproach32. Jupyterkernel diedmysteriously35. As permy lastemail…36. “Quick5-minsync” = 45minutes5. Can wemake itreal-time?17. Forgotto kill myprocess…sorry team!29. Worksperfectlyon mymachine27. Groundtruth isn’tactuallytrue33.Restartkernel, runall, pray13. CUDAout ofmemory1. Can weget 99.9%accuracy?4.Requirementschanged…again10. Whenwill themodel beproduction-ready?20. Weneedmore data3. A meetingcould havebeen anemail26. Testdataleaked intotraining set18. SSHconnectiondied mid-experiment21. Thelabels arecompletelywrong38. Nicepajamatop on thecall12. Servercrashedduring thelive demo25. Extremeclassimbalancestrikes again37. I’lldocumentthis later11. Who lefttrainingrunning ALLweekend?39. Petphotobombedthe video call

AI lab 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
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
  1. 9. The business need has… evolved
  2. 31. Wait… which cell did I run last?
  3. 7. This should be simple, right?
  4. 23. Dataset has 47 samples. Total.
  5. 34. This notebook is 2000 cells long
  6. 28. Loss went to NaN on step 1
  7. Free!
  8. 40. Internet died at demo time
  9. 15. Someone hogged all GPUs
  10. 6. Stakeholder ghosted after week 2
  11. 16. OOM killed at epoch 99 of 100
  12. 8. Just add ONE more feature before launch
  13. 19. Server rebooted overnight. RIP my results.
  14. 30. Forgot to shuffle the dataset
  15. 14. The server is suspiciously slow today
  16. 24. The data is too noisy to use
  17. 22. Who annotated this?!
  18. 2. Actually, let’s pivot the entire approach
  19. 32. Jupyter kernel died mysteriously
  20. 35. As per my last email…
  21. 36. “Quick 5-min sync” = 45 minutes
  22. 5. Can we make it real-time?
  23. 17. Forgot to kill my process… sorry team!
  24. 29. Works perfectly on my machine
  25. 27. Ground truth isn’t actually true
  26. 33. Restart kernel, run all, pray
  27. 13. CUDA out of memory
  28. 1. Can we get 99.9% accuracy?
  29. 4. Requirements changed… again
  30. 10. When will the model be production-ready?
  31. 20. We need more data
  32. 3. A meeting could have been an email
  33. 26. Test data leaked into training set
  34. 18. SSH connection died mid-experiment
  35. 21. The labels are completely wrong
  36. 38. Nice pajama top on the call
  37. 12. Server crashed during the live demo
  38. 25. Extreme class imbalance strikes again
  39. 37. I’ll document this later
  40. 11. Who left training running ALL weekend?
  41. 39. Pet photobombed the video call