Free!Relativelinenumbersin vimSpencerattendsbecause hewants a breakfrom workSomeonehas a freshdrink for themeetingHardware-in-the-loopismentioned/discussedSomeone inTuscon asks aquestion thatisn’t repeatedfor ZoomPresenterreusesold slidesSDR(s) arementioned/discussedTusconintroducestheir newhires, but notCentennial’s“So I didn’tmake slidestoday, I thoughtwe’d just do ademonstrationinstead”Codedoesn’trun/workFPGA(s) arementioned/discussedTuscon asks aleadingquestion just sothey cananswer itthemselvesCodeworks/runson firstattemptUses emacs,notepad, orother text editor(not VSCode orother IDE)Cable testing ismentioned/discussedCalibration ismentioned/discussedTuscon doesn’tlet Centennialinto the Zoombefore themeeting startsTusconforgets tounmutetheir audioTuscon hassideconversationsover thepresenter“Hey, canyou guyshear usOK?”Meetingruns longerthan 1 hourField testing ismentioned/discussedOWL tracksa randomperson whois notspeakingSomeonefromChantilyspeaksSlide is atleast 80%wordsAaron forgetsto show up formeeting/showsup lateSomeone inCentennialtakes over andexplainsconceptquicker/betterHope fixestechnicaldifficulties inthe middle ofthe meetngSimulation(s) arementioned/discussedHorriblevim colorschemeHyperfixateson a supernicheconceptSomeonestrugglesto log in toa systemUsesvimSomeone inCentennialfalls asleepduringmeetingGain/loss testing ismentioned/discussedPresentersays theycreatedslides day ofSomeonerantsaboutXMidasSomeonealmostfalls out oftheir chairFree!Relativelinenumbersin vimSpencerattendsbecause hewants a breakfrom workSomeonehas a freshdrink for themeetingHardware-in-the-loopismentioned/discussedSomeone inTuscon asks aquestion thatisn’t repeatedfor ZoomPresenterreusesold slidesSDR(s) arementioned/discussedTusconintroducestheir newhires, but notCentennial’s“So I didn’tmake slidestoday, I thoughtwe’d just do ademonstrationinstead”Codedoesn’trun/workFPGA(s) arementioned/discussedTuscon asks aleadingquestion just sothey cananswer itthemselvesCodeworks/runson firstattemptUses emacs,notepad, orother text editor(not VSCode orother IDE)Cable testing ismentioned/discussedCalibration ismentioned/discussedTuscon doesn’tlet Centennialinto the Zoombefore themeeting startsTusconforgets tounmutetheir audioTuscon hassideconversationsover thepresenter“Hey, canyou guyshear usOK?”Meetingruns longerthan 1 hourField testing ismentioned/discussedOWL tracksa randomperson whois notspeakingSomeonefromChantilyspeaksSlide is atleast 80%wordsAaron forgetsto show up formeeting/showsup lateSomeone inCentennialtakes over andexplainsconceptquicker/betterHope fixestechnicaldifficulties inthe middle ofthe meetngSimulation(s) arementioned/discussedHorriblevim colorschemeHyperfixateson a supernicheconceptSomeonestrugglesto log in toa systemUsesvimSomeone inCentennialfalls asleepduringmeetingGain/loss testing ismentioned/discussedPresentersays theycreatedslides day ofSomeonerantsaboutXMidasSomeonealmostfalls out oftheir chair

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