Presentersays theycreatedslides day ofSomeone inCentennialfalls asleepduringmeeting“So I didn’tmake slidestoday, I thoughtwe’d just do ademonstrationinstead”Hyperfixateson a supernicheconceptUses emacs,notepad, orother text editor(not VSCode orother IDE)Meetingruns longerthan 1 hourSlide is atleast 80%wordsFree!Presenterreusesold slidesCodeworks/runson firstattemptField testing ismentioned/discussedHorriblevim colorschemeCable testing ismentioned/discussedTuscon doesn’tlet Centennialinto the Zoombefore themeeting startsGain/loss testing ismentioned/discussedSomeonealmostfalls out oftheir chairSomeone inCentennialtakes over andexplainsconceptquicker/betterTuscon asks aleadingquestion just sothey cananswer itthemselvesHardware-in-the-loopismentioned/discussedAaron forgetsto show up formeeting/showsup lateOWL tracksa randomperson whois notspeakingCodedoesn’trun/workUsesvimSomeonerantsaboutXMidasSomeonestrugglesto log in toa systemTusconintroducestheir newhires, but notCentennial’sHope fixestechnicaldifficulties inthe middle ofthe meetngSomeone inTuscon asks aquestion thatisn’t repeatedfor ZoomSpencerattendsbecause hewants a breakfrom workSomeonefromChantilyspeaksTuscon hassideconversationsover thepresenterSimulation(s) arementioned/discussedSDR(s) arementioned/discussedSomeonehas a freshdrink for themeetingCalibration ismentioned/discussedFPGA(s) arementioned/discussedTusconforgets tounmutetheir audio“Hey, canyou guyshear usOK?”Relativelinenumbersin vimPresentersays theycreatedslides day ofSomeone inCentennialfalls asleepduringmeeting“So I didn’tmake slidestoday, I thoughtwe’d just do ademonstrationinstead”Hyperfixateson a supernicheconceptUses emacs,notepad, orother text editor(not VSCode orother IDE)Meetingruns longerthan 1 hourSlide is atleast 80%wordsFree!Presenterreusesold slidesCodeworks/runson firstattemptField testing ismentioned/discussedHorriblevim colorschemeCable testing ismentioned/discussedTuscon doesn’tlet Centennialinto the Zoombefore themeeting startsGain/loss testing ismentioned/discussedSomeonealmostfalls out oftheir chairSomeone inCentennialtakes over andexplainsconceptquicker/betterTuscon asks aleadingquestion just sothey cananswer itthemselvesHardware-in-the-loopismentioned/discussedAaron forgetsto show up formeeting/showsup lateOWL tracksa randomperson whois notspeakingCodedoesn’trun/workUsesvimSomeonerantsaboutXMidasSomeonestrugglesto log in toa systemTusconintroducestheir newhires, but notCentennial’sHope fixestechnicaldifficulties inthe middle ofthe meetngSomeone inTuscon asks aquestion thatisn’t repeatedfor ZoomSpencerattendsbecause hewants a breakfrom workSomeonefromChantilyspeaksTuscon hassideconversationsover thepresenterSimulation(s) arementioned/discussedSDR(s) arementioned/discussedSomeonehas a freshdrink for themeetingCalibration ismentioned/discussedFPGA(s) arementioned/discussedTusconforgets tounmutetheir audio“Hey, canyou guyshear usOK?”Relativelinenumbersin vim

New Hire 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
  1. Presenter says they created slides day of
  2. Someone in Centennial falls asleep during meeting
  3. “So I didn’t make slides today, I thought we’d just do a demonstration instead”
  4. Hyperfixates on a super niche concept
  5. Uses emacs, notepad, or other text editor (not VSCode or other IDE)
  6. Meeting runs longer than 1 hour
  7. Slide is at least 80% words
  8. Free!
  9. Presenter reuses old slides
  10. Code works/runs on first attempt
  11. Field testing is mentioned/discussed
  12. Horrible vim color scheme
  13. Cable testing is mentioned/discussed
  14. Tuscon doesn’t let Centennial into the Zoom before the meeting starts
  15. Gain/loss testing is mentioned/discussed
  16. Someone almost falls out of their chair
  17. Someone in Centennial takes over and explains concept quicker/better
  18. Tuscon asks a leading question just so they can answer it themselves
  19. Hardware-in-the-loop is mentioned/discussed
  20. Aaron forgets to show up for meeting/shows up late
  21. OWL tracks a random person who is not speaking
  22. Code doesn’t run/work
  23. Uses vim
  24. Someone rants about XMidas
  25. Someone struggles to log in to a system
  26. Tuscon introduces their new hires, but not Centennial’s
  27. Hope fixes technical difficulties in the middle of the meetng
  28. Someone in Tuscon asks a question that isn’t repeated for Zoom
  29. Spencer attends because he wants a break from work
  30. Someone from Chantily speaks
  31. Tuscon has side conversations over the presenter
  32. Simulation(s) are mentioned/discussed
  33. SDR(s) are mentioned/discussed
  34. Someone has a fresh drink for the meeting
  35. Calibration is mentioned/discussed
  36. FPGA(s) are mentioned/discussed
  37. Tuscon forgets to unmute their audio
  38. “Hey, can you guys hear us OK?”
  39. Relative line numbers in vim