Used anobscurelibrary thatactuallyworkedFound a bugthat wasactually afeatureGot a codereviewwithout anysuggestedchangesHas amechanicalkeyboardHas a folderof unfinishedside projectsCallsthemselvesfull-stackWears ahoodie toworkDebugged aproblem for4 hours, onlyto find a typoSaid "It'sa feature,not a bug"Hopessomeonesasks themabout yourIDE themeStayedlate nightcodingSolved abug undertheshowerAccidentallydeleted theproductiondatabaseCollaboratedon opensourceprojectsRefactoredcode to bea work ofartStartedusing a stackbefore it wascoolDecided togive upcoding atsome pointDebuggedcode inunder 5minutesDebuggedcode whiledancing toyour favoritetunesWrote ascript toautomateboring tasksHas noisecancelingheadphonesWrote adocumentationthat wasactually usefulHates itwhen peoplecalls themfull-stackFixed a bugby creatinganother oneUsed anobscurelibrary thatactuallyworkedFound a bugthat wasactually afeatureGot a codereviewwithout anysuggestedchangesHas amechanicalkeyboardHas a folderof unfinishedside projectsCallsthemselvesfull-stackWears ahoodie toworkDebugged aproblem for4 hours, onlyto find a typoSaid "It'sa feature,not a bug"Hopessomeonesasks themabout yourIDE themeStayedlate nightcodingSolved abug undertheshowerAccidentallydeleted theproductiondatabaseCollaboratedon opensourceprojectsRefactoredcode to bea work ofartStartedusing a stackbefore it wascoolDecided togive upcoding atsome pointDebuggedcode inunder 5minutesDebuggedcode whiledancing toyour favoritetunesWrote ascript toautomateboring tasksHas noisecancelingheadphonesWrote adocumentationthat wasactually usefulHates itwhen peoplecalls themfull-stackFixed a bugby creatinganother one

DOMINGO - 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. Used an obscure library that actually worked
  2. Found a bug that was actually a feature
  3. Got a code review without any suggested changes
  4. Has a mechanical keyboard
  5. Has a folder of unfinished side projects
  6. Calls themselves full-stack
  7. Wears a hoodie to work
  8. Debugged a problem for 4 hours, only to find a typo
  9. Said "It's a feature, not a bug"
  10. Hopes someones asks them about your IDE theme
  11. Stayed late night coding
  12. Solved a bug under the shower
  13. Accidentally deleted the production database
  14. Collaborated on open source projects
  15. Refactored code to be a work of art
  16. Started using a stack before it was cool
  17. Decided to give up coding at some point
  18. Debugged code in under 5 minutes
  19. Debugged code while dancing to your favorite tunes
  20. Wrote a script to automate boring tasks
  21. Has noise canceling headphones
  22. Wrote a documentation that was actually useful
  23. Hates it when people calls them full-stack
  24. Fixed a bug by creating another one