rollbackproductionMake 6+revisionsfor yourCRSolve aproblemthat youcreatedyou push achangethat breaksa pipelinework onanythingrelated toSalesforceapplicationsrun into an issuewhile testingyour changeAFTERdeploying toproductionsomeonerevokes anapprovalon your crSpend 2+ hourson a problemthat turns out tobe one line ofcoderestart yourmachinebecausechime "isn'tworking"Have 5+reviews ofyourdesign docCreate 3+COEs inone weekabortanMCMyourchangeset failsvalidationyour codebreaksyouattend 6+hours ofmeetingsin one dayyour CRreceives6+ nitsyour crchangecausessev2forget toreset yourpasswordbefore itexpirescopied andpasted codefrom stackoverflow isCR approvedyour device isdeemednoncompliantyour ticketis blockedby legalyou getpaged ontheweekendyourconnectionsquestionseems a bittoo specificyou getsev2'd forfileuploadserviceyou getpagedafterhoursrollbackproductionMake 6+revisionsfor yourCRSolve aproblemthat youcreatedyou push achangethat breaksa pipelinework onanythingrelated toSalesforceapplicationsrun into an issuewhile testingyour changeAFTERdeploying toproductionsomeonerevokes anapprovalon your crSpend 2+ hourson a problemthat turns out tobe one line ofcoderestart yourmachinebecausechime "isn'tworking"Have 5+reviews ofyourdesign docCreate 3+COEs inone weekabortanMCMyourchangeset failsvalidationyour codebreaksyouattend 6+hours ofmeetingsin one dayyour CRreceives6+ nitsyour crchangecausessev2forget toreset yourpasswordbefore itexpirescopied andpasted codefrom stackoverflow isCR approvedyour device isdeemednoncompliantyour ticketis blockedby legalyou getpaged ontheweekendyourconnectionsquestionseems a bittoo specificyou getsev2'd forfileuploadserviceyou getpagedafterhours

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