“Hey, canyou guyshear usOK?”Someonealmostfalls out oftheir chairSpencerattendsbecause hewants a breakfrom workGain/loss testing ismentioned/discussedCodeworks/runson firstattemptTuscon hassideconversationsover thepresenterSomeonefromChantilyspeaksSimulation(s) arementioned/discussedHyperfixateson a supernicheconceptTusconintroducestheir newhires, but notCentennial’sUses emacs,notepad, orother text editor(not VSCode orother IDE)“So I didn’tmake slidestoday, I thoughtwe’d just do ademonstrationinstead”Aaron forgetsto show up formeeting/showsup lateCodedoesn’trun/workOWL tracksa randomperson whois notspeakingSomeonestrugglesto log in toa systemSomeone inCentennialtakes over andexplainsconceptquicker/betterFree!Hardware-in-the-loopismentioned/discussedSomeonehas a freshdrink for themeetingSDR(s) arementioned/discussedRelativelinenumbersin vimSomeone inTuscon asks aquestion thatisn’t repeatedfor ZoomSlide is atleast 80%wordsSomeone inCentennialfalls asleepduringmeetingUsesvimField testing ismentioned/discussedTuscon asks aleadingquestion just sothey cananswer itthemselvesCable testing ismentioned/discussedSomeonerantsaboutXMidasHope fixestechnicaldifficulties inthe middle ofthe meetngFPGA(s) arementioned/discussedCalibration ismentioned/discussedHorriblevim colorschemePresentersays theycreatedslides day ofPresenterreusesold slidesMeetingruns longerthan 1 hourTusconforgets tounmutetheir audioTuscon doesn’tlet Centennialinto the Zoombefore themeeting starts“Hey, canyou guyshear usOK?”Someonealmostfalls out oftheir chairSpencerattendsbecause hewants a breakfrom workGain/loss testing ismentioned/discussedCodeworks/runson firstattemptTuscon hassideconversationsover thepresenterSomeonefromChantilyspeaksSimulation(s) arementioned/discussedHyperfixateson a supernicheconceptTusconintroducestheir newhires, but notCentennial’sUses emacs,notepad, orother text editor(not VSCode orother IDE)“So I didn’tmake slidestoday, I thoughtwe’d just do ademonstrationinstead”Aaron forgetsto show up formeeting/showsup lateCodedoesn’trun/workOWL tracksa randomperson whois notspeakingSomeonestrugglesto log in toa systemSomeone inCentennialtakes over andexplainsconceptquicker/betterFree!Hardware-in-the-loopismentioned/discussedSomeonehas a freshdrink for themeetingSDR(s) arementioned/discussedRelativelinenumbersin vimSomeone inTuscon asks aquestion thatisn’t repeatedfor ZoomSlide is atleast 80%wordsSomeone inCentennialfalls asleepduringmeetingUsesvimField testing ismentioned/discussedTuscon asks aleadingquestion just sothey cananswer itthemselvesCable testing ismentioned/discussedSomeonerantsaboutXMidasHope fixestechnicaldifficulties inthe middle ofthe meetngFPGA(s) arementioned/discussedCalibration ismentioned/discussedHorriblevim colorschemePresentersays theycreatedslides day ofPresenterreusesold slidesMeetingruns longerthan 1 hourTusconforgets tounmutetheir audioTuscon doesn’tlet Centennialinto the Zoombefore themeeting starts

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