Wrote ascript toautomateboring tasksFound a bugthat wasactually afeatureRefactoredcode to bea work ofartHas amechanicalkeyboardAccidentallydeleted theproductiondatabaseDebuggedcode whiledancing toyour favoritetunesSolved abug undertheshowerStayedlate nightcodingDecided togive upcoding atsome pointUsed anobscurelibrary thatactuallyworkedCollaboratedon opensourceprojectsDebugged aproblem for4 hours, onlyto find a typoGot a codereviewwithout anysuggestedchangesWrote adocumentationthat wasactually usefulStartedusing a stackbefore it wascoolHopessomeonesasks themabout yourIDE themeDebuggedcode inunder 5minutesHates itwhen peoplecalls themfull-stackWears ahoodie toworkFixed a bugby creatinganother oneSaid "It'sa feature,not a bug"Has a folderof unfinishedside projectsHas noisecancelingheadphonesCallsthemselvesfull-stackWrote ascript toautomateboring tasksFound a bugthat wasactually afeatureRefactoredcode to bea work ofartHas amechanicalkeyboardAccidentallydeleted theproductiondatabaseDebuggedcode whiledancing toyour favoritetunesSolved abug undertheshowerStayedlate nightcodingDecided togive upcoding atsome pointUsed anobscurelibrary thatactuallyworkedCollaboratedon opensourceprojectsDebugged aproblem for4 hours, onlyto find a typoGot a codereviewwithout anysuggestedchangesWrote adocumentationthat wasactually usefulStartedusing a stackbefore it wascoolHopessomeonesasks themabout yourIDE themeDebuggedcode inunder 5minutesHates itwhen peoplecalls themfull-stackWears ahoodie toworkFixed a bugby creatinganother oneSaid "It'sa feature,not a bug"Has a folderof unfinishedside projectsHas noisecancelingheadphonesCallsthemselvesfull-stack

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