"//TODO Fix"has beenCommittedLonger thanYou've WorkedHereUser DidSomething theyRegret?Manually Edittheir ProductionChanges!"Can you make afeature like[feature thatalready exists waybetter as aseparate product]"Run a NewApplicationWritten by aThird Party withZeroDocumentationTheDocumentationwas Written bySomeone whoLeft theCompanyBug Report aftera Release forSomething thathas AlwaysBeen BrokenA Whole AppExists in theEcosystem andNo One ToldYou About ItEveryone OnlyKnows a Pieceabout an OlderConcept orFeatureThe File isOlderthan YouAreBug Report onFeature X afterDeployment.Client Tested Xin QAEnvironment"Can you doX?" TheProjectAlreadyDoes XBug Report thatYour LastDeployment Brokea Feature theTeam Didn't KnowExistedMore than 3Versions of theSame SoftwareInstalled on theSame MachineIT Issue isStoppedDead byClient ITDepartmentThis BugReport is aFeatureRequest inDisguiseYour IL Mergedyour PR withoutTesting it andNow your PMsays it's BrokenThe BuildBroke withoutthe TeamChangingAnythingCode that's WayMore Complicatedthan what itNeeded to be for aVery SimpleConceptClient Insists aFeature hasAlways Workeda Specific Waywhen it ProvablyHasn'tSecretPage on aProductionSite"Does anyoneknow whatversion isactually inproduction rightnow?""Ignore thaterror it'salways beenthere"Client CompletelyMisunderstood aProposed Changeand wants aRollback or Patchafter DeploymentNo One Knows why aFeature Breaks andthe Accepted way toHandle it is toChange DatabaseValues DirectlyDiscover aFeatureUnrelated toYour CurrentTask NeverWorked at All"//TODO Fix"has beenCommittedLonger thanYou've WorkedHereUser DidSomething theyRegret?Manually Edittheir ProductionChanges!"Can you make afeature like[feature thatalready exists waybetter as aseparate product]"Run a NewApplicationWritten by aThird Party withZeroDocumentationTheDocumentationwas Written bySomeone whoLeft theCompanyBug Report aftera Release forSomething thathas AlwaysBeen BrokenA Whole AppExists in theEcosystem andNo One ToldYou About ItEveryone OnlyKnows a Pieceabout an OlderConcept orFeatureThe File isOlderthan YouAreBug Report onFeature X afterDeployment.Client Tested Xin QAEnvironment"Can you doX?" TheProjectAlreadyDoes XBug Report thatYour LastDeployment Brokea Feature theTeam Didn't KnowExistedMore than 3Versions of theSame SoftwareInstalled on theSame MachineIT Issue isStoppedDead byClient ITDepartmentThis BugReport is aFeatureRequest inDisguiseYour IL Mergedyour PR withoutTesting it andNow your PMsays it's BrokenThe BuildBroke withoutthe TeamChangingAnythingCode that's WayMore Complicatedthan what itNeeded to be for aVery SimpleConceptClient Insists aFeature hasAlways Workeda Specific Waywhen it ProvablyHasn'tSecretPage on aProductionSite"Does anyoneknow whatversion isactually inproduction rightnow?""Ignore thaterror it'salways beenthere"Client CompletelyMisunderstood aProposed Changeand wants aRollback or Patchafter DeploymentNo One Knows why aFeature Breaks andthe Accepted way toHandle it is toChange DatabaseValues DirectlyDiscover 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. "//TODO Fix" has been Committed Longer than You've Worked Here
  2. User Did Something they Regret? Manually Edit their Production Changes!
  3. "Can you make a feature like [feature that already exists way better as a separate product]"
  4. Run a New Application Written by a Third Party with Zero Documentation
  5. The Documentation was Written by Someone who Left the Company
  6. Bug Report after a Release for Something that has Always Been Broken
  7. A Whole App Exists in the Ecosystem and No One Told You About It
  8. Everyone Only Knows a Piece about an Older Concept or Feature
  9. The File is Older than You Are
  10. Bug Report on Feature X after Deployment. Client Tested X in QA Environment
  11. "Can you do X?" The Project Already Does X
  12. Bug Report that Your Last Deployment Broke a Feature the Team Didn't Know Existed
  13. More than 3 Versions of the Same Software Installed on the Same Machine
  14. IT Issue is Stopped Dead by Client IT Department
  15. This Bug Report is a Feature Request in Disguise
  16. Your IL Merged your PR without Testing it and Now your PM says it's Broken
  17. The Build Broke without the Team Changing Anything
  18. Code that's Way More Complicated than what it Needed to be for a Very Simple Concept
  19. Client Insists a Feature has Always Worked a Specific Way when it Provably Hasn't
  20. Secret Page on a Production Site
  21. "Does anyone know what version is actually in production right now?"
  22. "Ignore that error it's always been there"
  23. Client Completely Misunderstood a Proposed Change and wants a Rollback or Patch after Deployment
  24. No One Knows why a Feature Breaks and the Accepted way to Handle it is to Change Database Values Directly
  25. Discover a Feature Unrelated to Your Current Task Never Worked at All