Collaboratedon opensourceprojectsSaid "It'sa feature,not a bug"Has noisecancelingheadphonesGot a codereviewwithout anysuggestedchangesDebugged aproblem for4 hours, onlyto find a typoDecided togive upcoding atsome pointRefactoredcode to bea work ofartDebuggedcode whiledancing toyour favoritetunesDebuggedcode inunder 5minutesFixed a bugby creatinganother oneFound a bugthat wasactually afeatureStayedlate nightcodingHopessomeonesasks themabout yourIDE themeAccidentallydeleted theproductiondatabaseWrote adocumentationthat wasactually usefulCallsthemselvesfull-stackHas amechanicalkeyboardUsed anobscurelibrary thatactuallyworkedHates itwhen peoplecalls themfull-stackWears ahoodie toworkStartedusing a stackbefore it wascoolWrote ascript toautomateboring tasksSolved abug undertheshowerHas a folderof unfinishedside projectsCollaboratedon opensourceprojectsSaid "It'sa feature,not a bug"Has noisecancelingheadphonesGot a codereviewwithout anysuggestedchangesDebugged aproblem for4 hours, onlyto find a typoDecided togive upcoding atsome pointRefactoredcode to bea work ofartDebuggedcode whiledancing toyour favoritetunesDebuggedcode inunder 5minutesFixed a bugby creatinganother oneFound a bugthat wasactually afeatureStayedlate nightcodingHopessomeonesasks themabout yourIDE themeAccidentallydeleted theproductiondatabaseWrote adocumentationthat wasactually usefulCallsthemselvesfull-stackHas amechanicalkeyboardUsed anobscurelibrary thatactuallyworkedHates itwhen peoplecalls themfull-stackWears ahoodie toworkStartedusing a stackbefore it wascoolWrote ascript toautomateboring tasksSolved abug undertheshowerHas a folderof unfinishedside projects

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