Has amechanicalkeyboardStayedlate nightcodingUsed anobscurelibrary thatactuallyworkedCallsthemselvesfull-stackDebuggedcode inunder 5minutesSaid "It'sa feature,not a bug"Debuggedcode whiledancing toyour favoritetunesAccidentallydeleted theproductiondatabaseFixed a bugby creatinganother oneFound a bugthat wasactually afeatureDebugged aproblem for4 hours, onlyto find a typoDecided togive upcoding atsome pointWears ahoodie toworkHopessomeonesasks themabout yourIDE themeSolved abug undertheshowerWrote ascript toautomateboring tasksRefactoredcode to bea work ofartHas a folderof unfinishedside projectsStartedusing a stackbefore it wascoolCollaboratedon opensourceprojectsGot a codereviewwithout anysuggestedchangesHas noisecancelingheadphonesHates itwhen peoplecalls themfull-stackWrote adocumentationthat wasactually usefulHas amechanicalkeyboardStayedlate nightcodingUsed anobscurelibrary thatactuallyworkedCallsthemselvesfull-stackDebuggedcode inunder 5minutesSaid "It'sa feature,not a bug"Debuggedcode whiledancing toyour favoritetunesAccidentallydeleted theproductiondatabaseFixed a bugby creatinganother oneFound a bugthat wasactually afeatureDebugged aproblem for4 hours, onlyto find a typoDecided togive upcoding atsome pointWears ahoodie toworkHopessomeonesasks themabout yourIDE themeSolved abug undertheshowerWrote ascript toautomateboring tasksRefactoredcode to bea work ofartHas a folderof unfinishedside projectsStartedusing a stackbefore it wascoolCollaboratedon opensourceprojectsGot a codereviewwithout anysuggestedchangesHas noisecancelingheadphonesHates itwhen peoplecalls themfull-stackWrote adocumentationthat wasactually useful

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