Refactoredcode to bea work ofartFixed a bugby creatinganother oneFound a bugthat wasactually afeatureDecided togive upcoding atsome pointCollaboratedon opensourceprojectsHas noisecancelingheadphonesSolved abug undertheshowerSaid "It'sa feature,not a bug"Debuggedcode whiledancing toyour favoritetunesHopessomeonesasks themabout yourIDE themeAccidentallydeleted theproductiondatabaseHas a folderof unfinishedside projectsWrote ascript toautomateboring tasksHates itwhen peoplecalls themfull-stackCallsthemselvesfull-stackStayedlate nightcodingWears ahoodie toworkHas amechanicalkeyboardWrote adocumentationthat wasactually usefulUsed anobscurelibrary thatactuallyworkedGot a codereviewwithout anysuggestedchangesDebugged aproblem for4 hours, onlyto find a typoDebuggedcode inunder 5minutesStartedusing a stackbefore it wascoolRefactoredcode to bea work ofartFixed a bugby creatinganother oneFound a bugthat wasactually afeatureDecided togive upcoding atsome pointCollaboratedon opensourceprojectsHas noisecancelingheadphonesSolved abug undertheshowerSaid "It'sa feature,not a bug"Debuggedcode whiledancing toyour favoritetunesHopessomeonesasks themabout yourIDE themeAccidentallydeleted theproductiondatabaseHas a folderof unfinishedside projectsWrote ascript toautomateboring tasksHates itwhen peoplecalls themfull-stackCallsthemselvesfull-stackStayedlate nightcodingWears ahoodie toworkHas amechanicalkeyboardWrote adocumentationthat wasactually usefulUsed anobscurelibrary thatactuallyworkedGot a codereviewwithout anysuggestedchangesDebugged aproblem for4 hours, onlyto find a typoDebuggedcode inunder 5minutesStartedusing a stackbefore it wascool

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