Debugged aproblem for4 hours, onlyto find a typoFound a bugthat wasactually afeatureStartedusing a stackbefore it wascoolFixed a bugby creatinganother oneGot a codereviewwithout anysuggestedchangesUsed anobscurelibrary thatactuallyworkedHopessomeonesasks themabout yourIDE themeDebuggedcode inunder 5minutesHas amechanicalkeyboardHas noisecancelingheadphonesWears ahoodie toworkHas a folderof unfinishedside projectsSolved abug undertheshowerCallsthemselvesfull-stackDebuggedcode whiledancing toyour favoritetunesDecided togive upcoding atsome pointRefactoredcode to bea work ofartWrote adocumentationthat wasactually usefulSaid "It'sa feature,not a bug"Hates itwhen peoplecalls themfull-stackWrote ascript toautomateboring tasksStayedlate nightcodingCollaboratedon opensourceprojectsAccidentallydeleted theproductiondatabaseDebugged aproblem for4 hours, onlyto find a typoFound a bugthat wasactually afeatureStartedusing a stackbefore it wascoolFixed a bugby creatinganother oneGot a codereviewwithout anysuggestedchangesUsed anobscurelibrary thatactuallyworkedHopessomeonesasks themabout yourIDE themeDebuggedcode inunder 5minutesHas amechanicalkeyboardHas noisecancelingheadphonesWears ahoodie toworkHas a folderof unfinishedside projectsSolved abug undertheshowerCallsthemselvesfull-stackDebuggedcode whiledancing toyour favoritetunesDecided togive upcoding atsome pointRefactoredcode to bea work ofartWrote adocumentationthat wasactually usefulSaid "It'sa feature,not a bug"Hates itwhen peoplecalls themfull-stackWrote ascript toautomateboring tasksStayedlate nightcodingCollaboratedon opensourceprojectsAccidentallydeleted theproductiondatabase

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