Code that's WayMore Complicatedthan what itNeeded to be for aVery SimpleConceptEveryone OnlyKnows a Pieceabout an OlderConcept orFeature"//TODO Fix"has beenCommittedLonger thanYou've WorkedHereThe BuildBroke withoutthe TeamChangingAnythingTheDocumentationwas Written bySomeone whoLeft theCompanyNo One Knows why aFeature Breaks andthe Accepted way toHandle it is toChange DatabaseValues DirectlyIT Issue isStoppedDead byClient ITDepartment"Can you make afeature like[feature thatalready exists waybetter as aseparate product]"This BugReport is aFeatureRequest inDisguise"Ignore thaterror it'salways beenthere"Run a NewApplicationWritten by aThird Party withZeroDocumentationClient Insists aFeature hasAlways Workeda Specific Waywhen it ProvablyHasn'tSecretPage on aProductionSiteBug Report onFeature X afterDeployment.Client Tested Xin QAEnvironmentBug Report thatYour LastDeployment Brokea Feature theTeam Didn't KnowExistedBug Report aftera Release forSomething thathas AlwaysBeen BrokenUser DidSomething theyRegret?Manually Edittheir ProductionChanges!A Whole AppExists in theEcosystem andNo One ToldYou About ItThe File isOlderthan YouAreMore than 3Versions of theSame SoftwareInstalled on theSame MachineYour IL Mergedyour PR withoutTesting it andNow your PMsays it's BrokenClient CompletelyMisunderstood aProposed Changeand wants aRollback or Patchafter Deployment"Can you doX?" TheProjectAlreadyDoes X"Does anyoneknow whatversion isactually inproduction rightnow?"Discover aFeatureUnrelated toYour CurrentTask NeverWorked at AllCode that's WayMore Complicatedthan what itNeeded to be for aVery SimpleConceptEveryone OnlyKnows a Pieceabout an OlderConcept orFeature"//TODO Fix"has beenCommittedLonger thanYou've WorkedHereThe BuildBroke withoutthe TeamChangingAnythingTheDocumentationwas Written bySomeone whoLeft theCompanyNo One Knows why aFeature Breaks andthe Accepted way toHandle it is toChange DatabaseValues DirectlyIT Issue isStoppedDead byClient ITDepartment"Can you make afeature like[feature thatalready exists waybetter as aseparate product]"This BugReport is aFeatureRequest inDisguise"Ignore thaterror it'salways beenthere"Run a NewApplicationWritten by aThird Party withZeroDocumentationClient Insists aFeature hasAlways Workeda Specific Waywhen it ProvablyHasn'tSecretPage on aProductionSiteBug Report onFeature X afterDeployment.Client Tested Xin QAEnvironmentBug Report thatYour LastDeployment Brokea Feature theTeam Didn't KnowExistedBug Report aftera Release forSomething thathas AlwaysBeen BrokenUser DidSomething theyRegret?Manually Edittheir ProductionChanges!A Whole AppExists in theEcosystem andNo One ToldYou About ItThe File isOlderthan YouAreMore than 3Versions of theSame SoftwareInstalled on theSame MachineYour IL Mergedyour PR withoutTesting it andNow your PMsays it's BrokenClient CompletelyMisunderstood aProposed Changeand wants aRollback or Patchafter Deployment"Can you doX?" TheProjectAlreadyDoes X"Does anyoneknow whatversion isactually inproduction rightnow?"Discover aFeatureUnrelated toYour CurrentTask NeverWorked at All

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