17. Forgotto kill myprocess…sorry team!36. “Quick5-minsync” = 45minutes38. Nicepajamatop on thecall19. Serverrebootedovernight.RIP myresults.31. Wait…which celldid I runlast?32. Jupyterkernel diedmysteriously23. Datasethas 47samples.Total.15.Someonehogged allGPUs1. Can weget 99.9%accuracy?24. Thedata is toonoisy touse7. Thisshould besimple,right?29. Worksperfectlyon mymachine10. Whenwill themodel beproduction-ready?3. A meetingcould havebeen anemail18. SSHconnectiondied mid-experiment9. Thebusinessneed has…evolved35. As permy lastemail…20. Weneedmore data11. Who lefttrainingrunning ALLweekend?Free!13. CUDAout ofmemory4.Requirementschanged…again28. Losswent toNaN onstep 121. Thelabels arecompletelywrong8. Just addONE morefeaturebeforelaunch40.Internetdied atdemo time2. Actually,let’s pivotthe entireapproach27. Groundtruth isn’tactuallytrue14. Theserver issuspiciouslyslow today39. Petphotobombedthe video call22. Whoannotatedthis?!30. Forgotto shufflethedataset6.Stakeholderghostedafter week 234. Thisnotebookis 2000cells long12. Servercrashedduring thelive demo33.Restartkernel, runall, pray5. Can wemake itreal-time?26. Testdataleaked intotraining set25. Extremeclassimbalancestrikes again16. OOMkilled atepoch 99of 10037. I’lldocumentthis later17. Forgotto kill myprocess…sorry team!36. “Quick5-minsync” = 45minutes38. Nicepajamatop on thecall19. Serverrebootedovernight.RIP myresults.31. Wait…which celldid I runlast?32. Jupyterkernel diedmysteriously23. Datasethas 47samples.Total.15.Someonehogged allGPUs1. Can weget 99.9%accuracy?24. Thedata is toonoisy touse7. Thisshould besimple,right?29. Worksperfectlyon mymachine10. Whenwill themodel beproduction-ready?3. A meetingcould havebeen anemail18. SSHconnectiondied mid-experiment9. Thebusinessneed has…evolved35. As permy lastemail…20. Weneedmore data11. Who lefttrainingrunning ALLweekend?Free!13. CUDAout ofmemory4.Requirementschanged…again28. Losswent toNaN onstep 121. Thelabels arecompletelywrong8. Just addONE morefeaturebeforelaunch40.Internetdied atdemo time2. Actually,let’s pivotthe entireapproach27. Groundtruth isn’tactuallytrue14. Theserver issuspiciouslyslow today39. Petphotobombedthe video call22. Whoannotatedthis?!30. Forgotto shufflethedataset6.Stakeholderghostedafter week 234. Thisnotebookis 2000cells long12. Servercrashedduring thelive demo33.Restartkernel, runall, pray5. Can wemake itreal-time?26. Testdataleaked intotraining set25. Extremeclassimbalancestrikes again16. OOMkilled atepoch 99of 10037. I’lldocumentthis later

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