restart yourmachinebecausechime "isn'tworking"your CRreceives6+ nitsyour ticketis blockedby legalyour crchangecausessev2yourconnectionsquestionseems a bittoo specificyou getpagedafterhoursyou getpaged ontheweekendyou getsev2'd forfileuploadserviceCreate 3+COEs inone weekyour codebreaksyourollbackproductionsomeonerevokes anapprovalon your crrun into an issuewhile testingyour changeAFTERdeploying toproductioncopied andpasted codefrom stackoverflow isCR approvedyour device isdeemednoncompliantyou push achangethat breaksa pipelinework onanythingrelated toSalesforceapplicationsforget toreset yourpasswordbefore itexpiresabortanMCMSolve aproblemthat youcreatedHave 5+reviews ofyourdesign docMake 6+revisionsfor yourCRSpend 2+ hourson a problemthat turns out tobe one line ofcodeyourchangeset failsvalidationattend 6+hours ofmeetingsin one dayrestart yourmachinebecausechime "isn'tworking"your CRreceives6+ nitsyour ticketis blockedby legalyour crchangecausessev2yourconnectionsquestionseems a bittoo specificyou getpagedafterhoursyou getpaged ontheweekendyou getsev2'd forfileuploadserviceCreate 3+COEs inone weekyour codebreaksyourollbackproductionsomeonerevokes anapprovalon your crrun into an issuewhile testingyour changeAFTERdeploying toproductioncopied andpasted codefrom stackoverflow isCR approvedyour device isdeemednoncompliantyou push achangethat breaksa pipelinework onanythingrelated toSalesforceapplicationsforget toreset yourpasswordbefore itexpiresabortanMCMSolve aproblemthat youcreatedHave 5+reviews ofyourdesign docMake 6+revisionsfor yourCRSpend 2+ hourson a problemthat turns out tobe one line ofcodeyourchangeset failsvalidationattend 6+hours ofmeetingsin one day

Anti-Developer Bingo - 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. restart your machine because chime "isn't working"
  2. your CR receives 6+ nits
  3. your ticket is blocked by legal
  4. your cr change causes sev2
  5. your connections question seems a bit too specific
  6. you get paged after hours
  7. you get paged on the weekend
  8. you get sev2'd for fileupload service
  9. Create 3+ COEs in one week
  10. your code breaks you
  11. rollback production
  12. someone revokes an approval on your cr
  13. run into an issue while testing your change AFTER deploying to production
  14. copied and pasted code from stack overflow is CR approved
  15. your device is deemed noncompliant
  16. you push a change that breaks a pipeline
  17. work on anything related to Salesforce applications
  18. forget to reset your password before it expires
  19. abort an MCM
  20. Solve a problem that you created
  21. Have 5+ reviews of your design doc
  22. Make 6+ revisions for your CR
  23. Spend 2+ hours on a problem that turns out to be one line of code
  24. your change set fails validation
  25. attend 6+ hours of meetings in one day