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