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