Code that's WayMore Complicatedthan what itNeeded to be for aVery SimpleConceptYour IL Mergedyour PR withoutTesting it andNow your PMsays it's BrokenMore than 3Versions of theSame SoftwareInstalled on theSame MachineTheDocumentationwas Written bySomeone whoLeft theCompany"Does anyoneknow whatversion isactually inproduction rightnow?"IT Issue isStoppedDead byClient ITDepartment"Can you make afeature like[feature thatalready exists waybetter as aseparate product]"User DidSomething theyRegret?Manually Edittheir ProductionChanges!Discover aFeatureUnrelated toYour CurrentTask NeverWorked at All"//TODO Fix"has beenCommittedLonger thanYou've WorkedHereThis BugReport is aFeatureRequest inDisguiseClient CompletelyMisunderstood aProposed Changeand wants aRollback or Patchafter DeploymentRun a NewApplicationWritten by aThird Party withZeroDocumentationBug Report onFeature X afterDeployment.Client Tested Xin QAEnvironmentSecretPage on aProductionSiteEveryone OnlyKnows a Pieceabout an OlderConcept orFeatureBug Report thatYour LastDeployment Brokea Feature theTeam Didn't KnowExistedNo One Knows why aFeature Breaks andthe Accepted way toHandle it is toChange DatabaseValues Directly"Ignore thaterror it'salways beenthere"Bug Report aftera Release forSomething thathas AlwaysBeen BrokenA Whole AppExists in theEcosystem andNo One ToldYou About It"Can you doX?" TheProjectAlreadyDoes XThe File isOlderthan YouAreThe BuildBroke withoutthe TeamChangingAnythingClient Insists aFeature hasAlways Workeda Specific Waywhen it ProvablyHasn'tCode that's WayMore Complicatedthan what itNeeded to be for aVery SimpleConceptYour IL Mergedyour PR withoutTesting it andNow your PMsays it's BrokenMore than 3Versions of theSame SoftwareInstalled on theSame MachineTheDocumentationwas Written bySomeone whoLeft theCompany"Does anyoneknow whatversion isactually inproduction rightnow?"IT Issue isStoppedDead byClient ITDepartment"Can you make afeature like[feature thatalready exists waybetter as aseparate product]"User DidSomething theyRegret?Manually Edittheir ProductionChanges!Discover aFeatureUnrelated toYour CurrentTask NeverWorked at All"//TODO Fix"has beenCommittedLonger thanYou've WorkedHereThis BugReport is aFeatureRequest inDisguiseClient CompletelyMisunderstood aProposed Changeand wants aRollback or Patchafter DeploymentRun a NewApplicationWritten by aThird Party withZeroDocumentationBug Report onFeature X afterDeployment.Client Tested Xin QAEnvironmentSecretPage on aProductionSiteEveryone OnlyKnows a Pieceabout an OlderConcept orFeatureBug Report thatYour LastDeployment Brokea Feature theTeam Didn't KnowExistedNo One Knows why aFeature Breaks andthe Accepted way toHandle it is toChange DatabaseValues Directly"Ignore thaterror it'salways beenthere"Bug Report aftera Release forSomething thathas AlwaysBeen BrokenA Whole AppExists in theEcosystem andNo One ToldYou About It"Can you doX?" TheProjectAlreadyDoes XThe File isOlderthan YouAreThe BuildBroke withoutthe TeamChangingAnythingClient Insists aFeature hasAlways Workeda Specific Waywhen it ProvablyHasn't

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