your device isdeemednoncompliantrun into an issuewhile testingyour changeAFTERdeploying toproductionCreate 3+COEs inone weekattend 6+hours ofmeetingsin one dayyourchangeset failsvalidationMake 6+revisionsfor yourCRyou push achangethat breaksa pipelinesomeonerevokes anapprovalon your crrollbackproductionyourconnectionsquestionseems a bittoo specificSpend 2+ hourson a problemthat turns out tobe one line ofcodeSolve aproblemthat youcreatedrestart yourmachinebecausechime "isn'tworking"copied andpasted codefrom stackoverflow isCR approvedyour crchangecausessev2abortanMCMHave 5+reviews ofyourdesign docwork onanythingrelated toSalesforceapplicationsyou getsev2'd forfileuploadserviceyou getpaged ontheweekendyour ticketis blockedby legalyou getpagedafterhoursyour CRreceives6+ nitsyour codebreaksyouforget toreset yourpasswordbefore itexpiresyour device isdeemednoncompliantrun into an issuewhile testingyour changeAFTERdeploying toproductionCreate 3+COEs inone weekattend 6+hours ofmeetingsin one dayyourchangeset failsvalidationMake 6+revisionsfor yourCRyou push achangethat breaksa pipelinesomeonerevokes anapprovalon your crrollbackproductionyourconnectionsquestionseems a bittoo specificSpend 2+ hourson a problemthat turns out tobe one line ofcodeSolve aproblemthat youcreatedrestart yourmachinebecausechime "isn'tworking"copied andpasted codefrom stackoverflow isCR approvedyour crchangecausessev2abortanMCMHave 5+reviews ofyourdesign docwork onanythingrelated toSalesforceapplicationsyou getsev2'd forfileuploadserviceyou getpaged ontheweekendyour ticketis blockedby legalyou getpagedafterhoursyour CRreceives6+ nitsyour codebreaksyouforget toreset yourpasswordbefore itexpires

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