Says“right” andsomeonerespondsSays weshould knowsomething, buthasn’t been inany lectureKurt usessomethingother thanterminal orqpdfviewComplaintsaboutmultipleemailaddressesNostalgicabout oldLinuxWon’tanswerstudent’squestionReferences arelevantmodern-dayprogram tool(e.g. Pandas)Says “youshould knowthis” when wedon’t have areason toFamilymoment(e.g. hangsup on sister)MentionsboatsWon’t listento studentquestion ifhe ‘wentover it’Flexesabout usingemailthrough muttSomethingabout emacs,“but I don’thate it, I’m justa vim guy”Callsfunctionallanguagessuperior (neveruses them)DoxxesstudentRefers tocode orcoding asartTouchesstudent (anyphysicalcontact)Tries tobringdown theTux serverTalks aboutpersonal lifemore thanthe topicComplainingabout OOPlanguageBulliessomeoneTellssomeone toput theirphone awayMakes apassive-aggressivecommentActuallygoes oversomethingbefore quizGatekeepsShowsfavoritismtowardsstudents“We wentover that” inresponse toquestion (hedid not)Dissesarrowkeys andor mouseTells storywith no clearmoral orconclusionUses ‘youknow’ afterintroducing ausefulconceptUses the word“elegant”unironicallyabout anyKurt languageMisogynyGetsarrestedand/orpulled overUses weirdexpression(or usesexpressionwrong)Goes onananarchistrantUsesbrowser outof terminalduring thelectureBrings up thingwe don’t knowthat will(probably)never come upagainEnds rant withvariation of‘come on guys,we’re betterthan this’Walks inat least 5minuteslateComplaintsaboutMicrosoftChecks theman page(the guydoes that,not you)Mentionspornography(again)Calls vimmagical,the best,etcForgetsterminalcommandMentionsthe gradecurveComplementsJS, Python3,Java or C#Usesmultipleterminalsat once“Let's say”actuallymakessenseGives actualexample of whywe would needany of this (notincluding C)Mutters “itshouldn’tdo that”Says“right” andsomeonerespondsSays weshould knowsomething, buthasn’t been inany lectureKurt usessomethingother thanterminal orqpdfviewComplaintsaboutmultipleemailaddressesNostalgicabout oldLinuxWon’tanswerstudent’squestionReferences arelevantmodern-dayprogram tool(e.g. Pandas)Says “youshould knowthis” when wedon’t have areason toFamilymoment(e.g. hangsup on sister)MentionsboatsWon’t listento studentquestion ifhe ‘wentover it’Flexesabout usingemailthrough muttSomethingabout emacs,“but I don’thate it, I’m justa vim guy”Callsfunctionallanguagessuperior (neveruses them)DoxxesstudentRefers tocode orcoding asartTouchesstudent (anyphysicalcontact)Tries tobringdown theTux serverTalks aboutpersonal lifemore thanthe topicComplainingabout OOPlanguageBulliessomeoneTellssomeone toput theirphone awayMakes apassive-aggressivecommentActuallygoes oversomethingbefore quizGatekeepsShowsfavoritismtowardsstudents“We wentover that” inresponse toquestion (hedid not)Dissesarrowkeys andor mouseTells storywith no clearmoral orconclusionUses ‘youknow’ afterintroducing ausefulconceptUses the word“elegant”unironicallyabout anyKurt languageMisogynyGetsarrestedand/orpulled overUses weirdexpression(or usesexpressionwrong)Goes onananarchistrantUsesbrowser outof terminalduring thelectureBrings up thingwe don’t knowthat will(probably)never come upagainEnds rant withvariation of‘come on guys,we’re betterthan this’Walks inat least 5minuteslateComplaintsaboutMicrosoftChecks theman page(the guydoes that,not you)Mentionspornography(again)Calls vimmagical,the best,etcForgetsterminalcommandMentionsthe gradecurveComplementsJS, Python3,Java or C#Usesmultipleterminalsat once“Let's say”actuallymakessenseGives actualexample of whywe would needany of this (notincluding C)Mutters “itshouldn’tdo that”

Kurt. - 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
40
41
42
43
44
45
46
47
48
49
50
  1. Says “right” and someone responds
  2. Says we should know something, but hasn’t been in any lecture
  3. Kurt uses something other than terminal or qpdfview
  4. Complaints about multiple email addresses
  5. Nostalgic about old Linux
  6. Won’t answer student’s question
  7. References a relevant modern-day program tool (e.g. Pandas)
  8. Says “you should know this” when we don’t have a reason to
  9. Family moment (e.g. hangs up on sister)
  10. Mentions boats
  11. Won’t listen to student question if he ‘went over it’
  12. Flexes about using email through mutt
  13. Something about emacs, “but I don’t hate it, I’m just a vim guy”
  14. Calls functional languages superior (never uses them)
  15. Doxxes student
  16. Refers to code or coding as art
  17. Touches student (any physical contact)
  18. Tries to bring down the Tux server
  19. Talks about personal life more than the topic
  20. Complaining about OOP language
  21. Bullies someone
  22. Tells someone to put their phone away
  23. Makes a passive-aggressive comment
  24. Actually goes over something before quiz
  25. Gatekeeps
  26. Shows favoritism towards students
  27. “We went over that” in response to question (he did not)
  28. Disses arrow keys and or mouse
  29. Tells story with no clear moral or conclusion
  30. Uses ‘you know’ after introducing a useful concept
  31. Uses the word “elegant” unironically about any Kurt language
  32. Misogyny
  33. Gets arrested and/or pulled over
  34. Uses weird expression (or uses expression wrong)
  35. Goes on an anarchist rant
  36. Uses browser out of terminal during the lecture
  37. Brings up thing we don’t know that will (probably) never come up again
  38. Ends rant with variation of ‘come on guys, we’re better than this’
  39. Walks in at least 5 minutes late
  40. Complaints about Microsoft
  41. Checks the man page (the guy does that, not you)
  42. Mentions pornography (again)
  43. Calls vim magical, the best, etc
  44. Forgets terminal command
  45. Mentions the grade curve
  46. Complements JS, Python3, Java or C#
  47. Uses multiple terminals at once
  48. “Let's say” actually makes sense
  49. Gives actual example of why we would need any of this (not including C)
  50. Mutters “it shouldn’t do that”