Tuscon asks aleadingquestion just sothey cananswer itthemselvesSomeonefromChantilyspeaksTusconforgets tounmutetheir audioSimulation(s) arementioned/discussedTuscon doesn’tlet Centennialinto the Zoombefore themeeting startsSomeonerantsaboutXMidasSomeone inTuscon asks aquestion thatisn’t repeatedfor ZoomSpencerattendsbecause hewants a breakfrom workUses emacs,notepad, orother text editor(not VSCode orother IDE)FPGA(s) arementioned/discussedCodeworks/runson firstattemptTusconintroducestheir newhires, but notCentennial’sOWL tracksa randomperson whois notspeakingAaron forgetsto show up formeeting/showsup lateHorriblevim colorschemePresenterreusesold slidesSomeonehas a freshdrink for themeetingHope fixestechnicaldifficulties inthe middle ofthe meetngRelativelinenumbersin vimFree!Slide is atleast 80%wordsCable testing ismentioned/discussedSDR(s) arementioned/discussedField testing ismentioned/discussedSomeone inCentennialtakes over andexplainsconceptquicker/better“So I didn’tmake slidestoday, I thoughtwe’d just do ademonstrationinstead”Codedoesn’trun/workSomeonestrugglesto log in toa systemTuscon hassideconversationsover thepresenterUsesvimSomeonealmostfalls out oftheir chairMeetingruns longerthan 1 hourSomeone inCentennialfalls asleepduringmeeting“Hey, canyou guyshear usOK?”Hyperfixateson a supernicheconceptGain/loss testing ismentioned/discussedHardware-in-the-loopismentioned/discussedPresentersays theycreatedslides day ofCalibration ismentioned/discussedTuscon asks aleadingquestion just sothey cananswer itthemselvesSomeonefromChantilyspeaksTusconforgets tounmutetheir audioSimulation(s) arementioned/discussedTuscon doesn’tlet Centennialinto the Zoombefore themeeting startsSomeonerantsaboutXMidasSomeone inTuscon asks aquestion thatisn’t repeatedfor ZoomSpencerattendsbecause hewants a breakfrom workUses emacs,notepad, orother text editor(not VSCode orother IDE)FPGA(s) arementioned/discussedCodeworks/runson firstattemptTusconintroducestheir newhires, but notCentennial’sOWL tracksa randomperson whois notspeakingAaron forgetsto show up formeeting/showsup lateHorriblevim colorschemePresenterreusesold slidesSomeonehas a freshdrink for themeetingHope fixestechnicaldifficulties inthe middle ofthe meetngRelativelinenumbersin vimFree!Slide is atleast 80%wordsCable testing ismentioned/discussedSDR(s) arementioned/discussedField testing ismentioned/discussedSomeone inCentennialtakes over andexplainsconceptquicker/better“So I didn’tmake slidestoday, I thoughtwe’d just do ademonstrationinstead”Codedoesn’trun/workSomeonestrugglesto log in toa systemTuscon hassideconversationsover thepresenterUsesvimSomeonealmostfalls out oftheir chairMeetingruns longerthan 1 hourSomeone inCentennialfalls asleepduringmeeting“Hey, canyou guyshear usOK?”Hyperfixateson a supernicheconceptGain/loss testing ismentioned/discussedHardware-in-the-loopismentioned/discussedPresentersays theycreatedslides day ofCalibration ismentioned/discussed

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