18. SSHconnectiondied mid-experiment21. Thelabels arecompletelywrong14. Theserver issuspiciouslyslow today20. Weneedmore data37. I’lldocumentthis later19. Serverrebootedovernight.RIP myresults.31. Wait…which celldid I runlast?36. “Quick5-minsync” = 45minutes6.Stakeholderghostedafter week 25. Can wemake itreal-time?38. Nicepajamatop on thecall28. Losswent toNaN onstep 111. Who lefttrainingrunning ALLweekend?39. Petphotobombedthe video call4.Requirementschanged…again15.Someonehogged allGPUs40.Internetdied atdemo time16. OOMkilled atepoch 99of 1003. A meetingcould havebeen anemail9. Thebusinessneed has…evolved30. Forgotto shufflethedataset10. Whenwill themodel beproduction-ready?2. Actually,let’s pivotthe entireapproach8. Just addONE morefeaturebeforelaunch34. Thisnotebookis 2000cells long22. Whoannotatedthis?!17. Forgotto kill myprocess…sorry team!1. Can weget 99.9%accuracy?35. As permy lastemail…24. Thedata is toonoisy touse25. Extremeclassimbalancestrikes again29. Worksperfectlyon mymachine33.Restartkernel, runall, pray23. Datasethas 47samples.Total.7. Thisshould besimple,right?32. Jupyterkernel diedmysteriously13. CUDAout ofmemory27. Groundtruth isn’tactuallytrueFree!12. Servercrashedduring thelive demo26. Testdataleaked intotraining set18. SSHconnectiondied mid-experiment21. Thelabels arecompletelywrong14. Theserver issuspiciouslyslow today20. Weneedmore data37. I’lldocumentthis later19. Serverrebootedovernight.RIP myresults.31. Wait…which celldid I runlast?36. “Quick5-minsync” = 45minutes6.Stakeholderghostedafter week 25. Can wemake itreal-time?38. Nicepajamatop on thecall28. Losswent toNaN onstep 111. Who lefttrainingrunning ALLweekend?39. Petphotobombedthe video call4.Requirementschanged…again15.Someonehogged allGPUs40.Internetdied atdemo time16. OOMkilled atepoch 99of 1003. A meetingcould havebeen anemail9. Thebusinessneed has…evolved30. Forgotto shufflethedataset10. Whenwill themodel beproduction-ready?2. Actually,let’s pivotthe entireapproach8. Just addONE morefeaturebeforelaunch34. Thisnotebookis 2000cells long22. Whoannotatedthis?!17. Forgotto kill myprocess…sorry team!1. Can weget 99.9%accuracy?35. As permy lastemail…24. Thedata is toonoisy touse25. Extremeclassimbalancestrikes again29. Worksperfectlyon mymachine33.Restartkernel, runall, pray23. Datasethas 47samples.Total.7. Thisshould besimple,right?32. Jupyterkernel diedmysteriously13. CUDAout ofmemory27. Groundtruth isn’tactuallytrueFree!12. Servercrashedduring thelive demo26. Testdataleaked intotraining set

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