“Hey, canyou guyshear usOK?”g++/debuggingis mentioned/discussedHorriblevim colorschemePresentersays theycreatedslides day ofSlide hasa useless/randomphotoSomeone inCentennialtakes over andexplainsconceptquicker/ betterFixestechnicaldifficulties inthe middle ofthe meetingSomeoneasks if thescreen shareis workingHyperfixateson a supernicheconceptSomeoneasks aquestion thatisn’t repeatedfor ZoomTusconintroducestheir newhires, but notCentennial’sRelativelinenumbersin vimCodedoesn’trun/ workPresentationends 20 minor moreearlyLinking ismentioned/discussedSlide isvague/unhelpfulSomeonestrugglesto log in toa systemSomeonefalls asleepduringmeetingOWL tracksa randomperson whois notspeakingUsesvimA slidehas typos/latexmistakesSomeonebrings afresh snackto themeetingAaron forgetsto show upfor meeting/shows up lateForgets tounmutetheiraudioSomeonealmostfalls out oftheir chairMeetingruns longerthan 1 hourSomeonerantsaboutXMidasSomeone asksa leadingquestion just sothey cananswer itthemselvesCompilingismentioned/discussedSlide is atleast 80%wordsCodeworks/ runson firstattemptBuilding ismentioned/discussedC/C++/C#ismentioned/discussedPresentergoes on a >=10 min tangentin middle ofpresentationSomeonehas a freshdrink for themeetingPresenterreusesold slidesSideconversationsover thepresenter“So I didn’tmake slidestoday, I thoughtwe’d just do ademonstrationinstead”Aaron getsbored andswitches awayfrom zoomduring themeetingObject-orientedprogrammingis mentioned/discussedUses emacs,notepad, orother text editor(not VSCode orother IDE)“Hey, canyou guyshear usOK?”g++/debuggingis mentioned/discussedHorriblevim colorschemePresentersays theycreatedslides day ofSlide hasa useless/randomphotoSomeone inCentennialtakes over andexplainsconceptquicker/ betterFixestechnicaldifficulties inthe middle ofthe meetingSomeoneasks if thescreen shareis workingHyperfixateson a supernicheconceptSomeoneasks aquestion thatisn’t repeatedfor ZoomTusconintroducestheir newhires, but notCentennial’sRelativelinenumbersin vimCodedoesn’trun/ workPresentationends 20 minor moreearlyLinking ismentioned/discussedSlide isvague/unhelpfulSomeonestrugglesto log in toa systemSomeonefalls asleepduringmeetingOWL tracksa randomperson whois notspeakingUsesvimA slidehas typos/latexmistakesSomeonebrings afresh snackto themeetingAaron forgetsto show upfor meeting/shows up lateForgets tounmutetheiraudioSomeonealmostfalls out oftheir chairMeetingruns longerthan 1 hourSomeonerantsaboutXMidasSomeone asksa leadingquestion just sothey cananswer itthemselvesCompilingismentioned/discussedSlide is atleast 80%wordsCodeworks/ runson firstattemptBuilding ismentioned/discussedC/C++/C#ismentioned/discussedPresentergoes on a >=10 min tangentin middle ofpresentationSomeonehas a freshdrink for themeetingPresenterreusesold slidesSideconversationsover thepresenter“So I didn’tmake slidestoday, I thoughtwe’d just do ademonstrationinstead”Aaron getsbored andswitches awayfrom zoomduring themeetingObject-orientedprogrammingis mentioned/discussedUses emacs,notepad, orother text editor(not VSCode orother IDE)

Untitled 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. “Hey, can you guys hear us OK?”
  2. g++/debugging is mentioned/ discussed
  3. Horrible vim color scheme
  4. Presenter says they created slides day of
  5. Slide has a useless/ random photo
  6. Someone in Centennial takes over and explains concept quicker/ better
  7. Fixes technical difficulties in the middle of the meeting
  8. Someone asks if the screen share is working
  9. Hyperfixates on a super niche concept
  10. Someone asks a question that isn’t repeated for Zoom
  11. Tuscon introduces their new hires, but not Centennial’s
  12. Relative line numbers in vim
  13. Code doesn’t run/ work
  14. Presentation ends 20 min or more early
  15. Linking is mentioned/discussed
  16. Slide is vague/ unhelpful
  17. Someone struggles to log in to a system
  18. Someone falls asleep during meeting
  19. OWL tracks a random person who is not speaking
  20. Uses vim
  21. A slide has typos/ latex mistakes
  22. Someone brings a fresh snack to the meeting
  23. Aaron forgets to show up for meeting/ shows up late
  24. Forgets to unmute their audio
  25. Someone almost falls out of their chair
  26. Meeting runs longer than 1 hour
  27. Someone rants about XMidas
  28. Someone asks a leading question just so they can answer it themselves
  29. Compiling is mentioned/ discussed
  30. Slide is at least 80% words
  31. Code works/ runs on first attempt
  32. Building is mentioned/ discussed
  33. C/C++/C# is mentioned/ discussed
  34. Presenter goes on a >= 10 min tangent in middle of presentation
  35. Someone has a fresh drink for the meeting
  36. Presenter reuses old slides
  37. Side conversations over the presenter
  38. “So I didn’t make slides today, I thought we’d just do a demonstration instead”
  39. Aaron gets bored and switches away from zoom during the meeting
  40. Object-oriented programming is mentioned/ discussed
  41. Uses emacs, notepad, or other text editor (not VSCode or other IDE)