Stayedlate nightcodingHas amechanicalkeyboardDecided togive upcoding atsome pointSolved abug undertheshowerRefactoredcode to bea work ofartDebuggedcode whiledancing toyour favoritetunesUsed anobscurelibrary thatactuallyworkedStartedusing a stackbefore it wascoolDebuggedcode inunder 5minutesDebugged aproblem for4 hours, onlyto find a typoSaid "It'sa feature,not a bug"Wears ahoodie toworkWrote adocumentationthat wasactually usefulFound a bugthat wasactually afeatureGot a codereviewwithout anysuggestedchangesWrote ascript toautomateboring tasksHas noisecancelingheadphonesAccidentallydeleted theproductiondatabaseCollaboratedon opensourceprojectsFixed a bugby creatinganother oneHates itwhen peoplecalls themfull-stackHopessomeonesasks themabout yourIDE themeCallsthemselvesfull-stackHas a folderof unfinishedside projectsStayedlate nightcodingHas amechanicalkeyboardDecided togive upcoding atsome pointSolved abug undertheshowerRefactoredcode to bea work ofartDebuggedcode whiledancing toyour favoritetunesUsed anobscurelibrary thatactuallyworkedStartedusing a stackbefore it wascoolDebuggedcode inunder 5minutesDebugged aproblem for4 hours, onlyto find a typoSaid "It'sa feature,not a bug"Wears ahoodie toworkWrote adocumentationthat wasactually usefulFound a bugthat wasactually afeatureGot a codereviewwithout anysuggestedchangesWrote ascript toautomateboring tasksHas noisecancelingheadphonesAccidentallydeleted theproductiondatabaseCollaboratedon opensourceprojectsFixed a bugby creatinganother oneHates itwhen peoplecalls themfull-stackHopessomeonesasks themabout yourIDE themeCallsthemselvesfull-stackHas 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. Stayed late night coding
  2. Has a mechanical keyboard
  3. Decided to give up coding at some point
  4. Solved a bug under the shower
  5. Refactored code to be a work of art
  6. Debugged code while dancing to your favorite tunes
  7. Used an obscure library that actually worked
  8. Started using a stack before it was cool
  9. Debugged code in under 5 minutes
  10. Debugged a problem for 4 hours, only to find a typo
  11. Said "It's a feature, not a bug"
  12. Wears a hoodie to work
  13. Wrote a documentation that was actually useful
  14. Found a bug that was actually a feature
  15. Got a code review without any suggested changes
  16. Wrote a script to automate boring tasks
  17. Has noise canceling headphones
  18. Accidentally deleted the production database
  19. Collaborated on open source projects
  20. Fixed a bug by creating another one
  21. Hates it when people calls them full-stack
  22. Hopes someones asks them about your IDE theme
  23. Calls themselves full-stack
  24. Has a folder of unfinished side projects