"Can you doX?" TheProjectAlreadyDoes XSecretPage on aProductionSite"//TODO Fix"has beenCommittedLonger thanYou've WorkedHereBug Report onFeature X afterDeployment.Client Tested Xin QAEnvironmentYour IL Mergedyour PR withoutTesting it andNow your PMsays it's BrokenClient CompletelyMisunderstood aProposed Changeand wants aRollback or Patchafter DeploymentUser DidSomething theyRegret?Manually Edittheir ProductionChanges!TheDocumentationwas Written bySomeone whoLeft theCompanyCode that's WayMore Complicatedthan what itNeeded to be for aVery SimpleConceptThe File isOlderthan YouAreIT Issue isStoppedDead byClient ITDepartmentBug Report aftera Release forSomething thathas AlwaysBeen BrokenBug Report thatYour LastDeployment Brokea Feature theTeam Didn't KnowExistedNo One Knows why aFeature Breaks andthe Accepted way toHandle it is toChange DatabaseValues DirectlyMore than 3Versions of theSame SoftwareInstalled on theSame MachineDiscover aFeatureUnrelated toYour CurrentTask NeverWorked at AllRun a NewApplicationWritten by aThird Party withZeroDocumentationThis BugReport is aFeatureRequest inDisguiseClient Insists aFeature hasAlways Workeda Specific Waywhen it ProvablyHasn't"Can you make afeature like[feature thatalready exists waybetter as aseparate product]"Everyone OnlyKnows a Pieceabout an OlderConcept orFeature"Does anyoneknow whatversion isactually inproduction rightnow?"A Whole AppExists in theEcosystem andNo One ToldYou About ItThe BuildBroke withoutthe TeamChangingAnything"Ignore thaterror it'salways beenthere""Can you doX?" TheProjectAlreadyDoes XSecretPage on aProductionSite"//TODO Fix"has beenCommittedLonger thanYou've WorkedHereBug Report onFeature X afterDeployment.Client Tested Xin QAEnvironmentYour IL Mergedyour PR withoutTesting it andNow your PMsays it's BrokenClient CompletelyMisunderstood aProposed Changeand wants aRollback or Patchafter DeploymentUser DidSomething theyRegret?Manually Edittheir ProductionChanges!TheDocumentationwas Written bySomeone whoLeft theCompanyCode that's WayMore Complicatedthan what itNeeded to be for aVery SimpleConceptThe File isOlderthan YouAreIT Issue isStoppedDead byClient ITDepartmentBug Report aftera Release forSomething thathas AlwaysBeen BrokenBug Report thatYour LastDeployment Brokea Feature theTeam Didn't KnowExistedNo One Knows why aFeature Breaks andthe Accepted way toHandle it is toChange DatabaseValues DirectlyMore than 3Versions of theSame SoftwareInstalled on theSame MachineDiscover aFeatureUnrelated toYour CurrentTask NeverWorked at AllRun a NewApplicationWritten by aThird Party withZeroDocumentationThis BugReport is aFeatureRequest inDisguiseClient Insists aFeature hasAlways Workeda Specific Waywhen it ProvablyHasn't"Can you make afeature like[feature thatalready exists waybetter as aseparate product]"Everyone OnlyKnows a Pieceabout an OlderConcept orFeature"Does anyoneknow whatversion isactually inproduction rightnow?"A Whole AppExists in theEcosystem andNo One ToldYou About ItThe BuildBroke withoutthe TeamChangingAnything"Ignore thaterror it'salways beenthere"

This is Fine - 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
25
  1. "Can you do X?" The Project Already Does X
  2. Secret Page on a Production Site
  3. "//TODO Fix" has been Committed Longer than You've Worked Here
  4. Bug Report on Feature X after Deployment. Client Tested X in QA Environment
  5. Your IL Merged your PR without Testing it and Now your PM says it's Broken
  6. Client Completely Misunderstood a Proposed Change and wants a Rollback or Patch after Deployment
  7. User Did Something they Regret? Manually Edit their Production Changes!
  8. The Documentation was Written by Someone who Left the Company
  9. Code that's Way More Complicated than what it Needed to be for a Very Simple Concept
  10. The File is Older than You Are
  11. IT Issue is Stopped Dead by Client IT Department
  12. Bug Report after a Release for Something that has Always Been Broken
  13. Bug Report that Your Last Deployment Broke a Feature the Team Didn't Know Existed
  14. No One Knows why a Feature Breaks and the Accepted way to Handle it is to Change Database Values Directly
  15. More than 3 Versions of the Same Software Installed on the Same Machine
  16. Discover a Feature Unrelated to Your Current Task Never Worked at All
  17. Run a New Application Written by a Third Party with Zero Documentation
  18. This Bug Report is a Feature Request in Disguise
  19. Client Insists a Feature has Always Worked a Specific Way when it Provably Hasn't
  20. "Can you make a feature like [feature that already exists way better as a separate product]"
  21. Everyone Only Knows a Piece about an Older Concept or Feature
  22. "Does anyone know what version is actually in production right now?"
  23. A Whole App Exists in the Ecosystem and No One Told You About It
  24. The Build Broke without the Team Changing Anything
  25. "Ignore that error it's always been there"