submittingon git is thehardest partof the psetsystem wasabstractedbefore youactuallyunderstood itcredit-nonrunning yourcode even thoyou changednothing, hopingthe compilerfigured itself out*ignorescompiler's42360warnings*attends helproom to forceyourself tostart the pset"jean/benare youbusy""ohhhmakessense,thank you"not surehow totest yourcode0x530x4F0x53proud to put C onyour resume, buthoping interviewernever asks youabout itwires arealways toolong onthe boardceo atraising yourhand firstduring labused 2-dayextensionterminalmakes youfeel like ahackerpracticallylives inL037living for thepuns (ex. toes'complements)"I will startthe next psetas soon asit's assigned"love seeingyourclassmates5x a weekwishingyou weremaddie theMUX oxrealized youcan't dobasicaddition orsubtractionforcedbesties withvalgrind andgdblovingthatweeklyadrenaline rushwhen you startpre-lab 5 minsbefore labfights forfront rowseatsubmittingon git is thehardest partof the psetsystem wasabstractedbefore youactuallyunderstood itcredit-nonrunning yourcode even thoyou changednothing, hopingthe compilerfigured itself out*ignorescompiler's42360warnings*attends helproom to forceyourself tostart the pset"jean/benare youbusy""ohhhmakessense,thank you"not surehow totest yourcode0x530x4F0x53proud to put C onyour resume, buthoping interviewernever asks youabout itwires arealways toolong onthe boardceo atraising yourhand firstduring labused 2-dayextensionterminalmakes youfeel like ahackerpracticallylives inL037living for thepuns (ex. toes'complements)"I will startthe next psetas soon asit's assigned"love seeingyourclassmates5x a weekwishingyou weremaddie theMUX oxrealized youcan't dobasicaddition orsubtractionforcedbesties withvalgrind andgdblovingthatweeklyadrenaline rushwhen you startpre-lab 5 minsbefore labfights forfront rowseat

CS 240 - 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
  1. submitting on git is the hardest part of the pset
  2. system was abstracted before you actually understood it
  3. credit-non
  4. running your code even tho you changed nothing, hoping the compiler figured itself out
  5. *ignores compiler's 42360 warnings*
  6. attends help room to force yourself to start the pset
  7. "jean/ben are you busy"
  8. "ohhh makes sense, thank you"
  9. not sure how to test your code
  10. 0x53 0x4F 0x53
  11. proud to put C on your resume, but hoping interviewer never asks you about it
  12. wires are always too long on the board
  13. ceo at raising your hand first during lab
  14. used 2-day extension
  15. terminal makes you feel like a hacker
  16. practically lives in L037
  17. living for the puns (ex. toes' complements)
  18. "I will start the next pset as soon as it's assigned"
  19. love seeing your classmates 5x a week
  20. wishing you were maddie the MUX ox
  21. realized you can't do basic addition or subtraction
  22. forced besties with valgrind and gdb
  23. lovingthat weekly adrenaline rush when you start pre-lab 5 mins before lab
  24. fights for front row seat