Codedoesn’trun/workSlide is atleast 80%wordsTuscon hassideconversationsover thepresenterFPGA(s) arementioned/discussedSomeonehas a freshdrink for themeetingSomeone inTuscon asks aquestion thatisn’t repeatedfor ZoomSpencerattendsbecause hewants a breakfrom workUses emacs,notepad, orother text editor(not VSCode orother IDE)Field testing ismentioned/discussedAaron forgetsto show up formeeting/showsup lateSomeone inCentennialfalls asleepduringmeetingCable testing ismentioned/discussedHope fixestechnicaldifficulties inthe middle ofthe meetngSomeone inCentennialtakes over andexplainsconceptquicker/betterHardware-in-the-loopismentioned/discussedTusconintroducestheir newhires, but notCentennial’sGain/loss testing ismentioned/discussedPresentersays theycreatedslides day ofSomeonealmostfalls out oftheir chairSomeonefromChantilyspeaksSomeonerantsaboutXMidas“So I didn’tmake slidestoday, I thoughtwe’d just do ademonstrationinstead”Presenterreusesold slidesSomeonestrugglesto log in toa systemSDR(s) arementioned/discussedHorriblevim colorschemeTuscon doesn’tlet Centennialinto the Zoombefore themeeting startsSimulation(s) arementioned/discussedCalibration ismentioned/discussedTuscon asks aleadingquestion just sothey cananswer itthemselvesCodeworks/runson firstattemptTusconforgets tounmutetheir audioUsesvimOWL tracksa randomperson whois notspeakingMeetingruns longerthan 1 hourHyperfixateson a supernicheconcept“Hey, canyou guyshear usOK?”Free!Relativelinenumbersin vimCodedoesn’trun/workSlide is atleast 80%wordsTuscon hassideconversationsover thepresenterFPGA(s) arementioned/discussedSomeonehas a freshdrink for themeetingSomeone inTuscon asks aquestion thatisn’t repeatedfor ZoomSpencerattendsbecause hewants a breakfrom workUses emacs,notepad, orother text editor(not VSCode orother IDE)Field testing ismentioned/discussedAaron forgetsto show up formeeting/showsup lateSomeone inCentennialfalls asleepduringmeetingCable testing ismentioned/discussedHope fixestechnicaldifficulties inthe middle ofthe meetngSomeone inCentennialtakes over andexplainsconceptquicker/betterHardware-in-the-loopismentioned/discussedTusconintroducestheir newhires, but notCentennial’sGain/loss testing ismentioned/discussedPresentersays theycreatedslides day ofSomeonealmostfalls out oftheir chairSomeonefromChantilyspeaksSomeonerantsaboutXMidas“So I didn’tmake slidestoday, I thoughtwe’d just do ademonstrationinstead”Presenterreusesold slidesSomeonestrugglesto log in toa systemSDR(s) arementioned/discussedHorriblevim colorschemeTuscon doesn’tlet Centennialinto the Zoombefore themeeting startsSimulation(s) arementioned/discussedCalibration ismentioned/discussedTuscon asks aleadingquestion just sothey cananswer itthemselvesCodeworks/runson firstattemptTusconforgets tounmutetheir audioUsesvimOWL tracksa randomperson whois notspeakingMeetingruns longerthan 1 hourHyperfixateson a supernicheconcept“Hey, canyou guyshear usOK?”Free!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. Code doesn’t run/work
  2. Slide is at least 80% words
  3. Tuscon has side conversations over the presenter
  4. FPGA(s) are mentioned/discussed
  5. Someone has a fresh drink for the meeting
  6. Someone in Tuscon asks a question that isn’t repeated for Zoom
  7. Spencer attends because he wants a break from work
  8. Uses emacs, notepad, or other text editor (not VSCode or other IDE)
  9. Field testing is mentioned/discussed
  10. Aaron forgets to show up for meeting/shows up late
  11. Someone in Centennial falls asleep during meeting
  12. Cable testing is mentioned/discussed
  13. Hope fixes technical difficulties in the middle of the meetng
  14. Someone in Centennial takes over and explains concept quicker/better
  15. Hardware-in-the-loop is mentioned/discussed
  16. Tuscon introduces their new hires, but not Centennial’s
  17. Gain/loss testing is mentioned/discussed
  18. Presenter says they created slides day of
  19. Someone almost falls out of their chair
  20. Someone from Chantily speaks
  21. Someone rants about XMidas
  22. “So I didn’t make slides today, I thought we’d just do a demonstration instead”
  23. Presenter reuses old slides
  24. Someone struggles to log in to a system
  25. SDR(s) are mentioned/discussed
  26. Horrible vim color scheme
  27. Tuscon doesn’t let Centennial into the Zoom before the meeting starts
  28. Simulation(s) are mentioned/discussed
  29. Calibration is mentioned/discussed
  30. Tuscon asks a leading question just so they can answer it themselves
  31. Code works/runs on first attempt
  32. Tuscon forgets to unmute their audio
  33. Uses vim
  34. OWL tracks a random person who is not speaking
  35. Meeting runs longer than 1 hour
  36. Hyperfixates on a super niche concept
  37. “Hey, can you guys hear us OK?”
  38. Free!
  39. Relative line numbers in vim