Got a codereviewwithout anysuggestedchangesHopessomeonesasks themabout yourIDE themeCallsthemselvesfull-stackStayedlate nightcodingHates itwhen peoplecalls themfull-stackCollaboratedon opensourceprojectsFixed a bugby creatinganother oneStartedusing a stackbefore it wascoolDebuggedcode whiledancing toyour favoritetunesHas noisecancelingheadphonesFound a bugthat wasactually afeatureRefactoredcode to bea work ofartDebugged aproblem for4 hours, onlyto find a typoWrote adocumentationthat wasactually usefulHas a folderof unfinishedside projectsAccidentallydeleted theproductiondatabaseWrote ascript toautomateboring tasksSaid "It'sa feature,not a bug"Debuggedcode inunder 5minutesWears ahoodie toworkHas amechanicalkeyboardSolved abug undertheshowerUsed anobscurelibrary thatactuallyworkedDecided togive upcoding atsome pointGot a codereviewwithout anysuggestedchangesHopessomeonesasks themabout yourIDE themeCallsthemselvesfull-stackStayedlate nightcodingHates itwhen peoplecalls themfull-stackCollaboratedon opensourceprojectsFixed a bugby creatinganother oneStartedusing a stackbefore it wascoolDebuggedcode whiledancing toyour favoritetunesHas noisecancelingheadphonesFound a bugthat wasactually afeatureRefactoredcode to bea work ofartDebugged aproblem for4 hours, onlyto find a typoWrote adocumentationthat wasactually usefulHas a folderof unfinishedside projectsAccidentallydeleted theproductiondatabaseWrote ascript toautomateboring tasksSaid "It'sa feature,not a bug"Debuggedcode inunder 5minutesWears ahoodie toworkHas amechanicalkeyboardSolved abug undertheshowerUsed anobscurelibrary thatactuallyworkedDecided togive upcoding atsome point

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