Create 3+COEs inone weekrestart yourmachinebecausechime "isn'tworking"yourconnectionsquestionseems a bittoo specificattend 6+hours ofmeetingsin one daycopied andpasted codefrom stackoverflow isCR approvedyou push achangethat breaksa pipelineyour crchangecausessev2your CRreceives6+ nitsyou getpagedafterhoursSolve aproblemthat youcreatedMake 6+revisionsfor yourCRyourchangeset failsvalidationyou getpaged ontheweekendHave 5+reviews ofyourdesign docrollbackproductionabortanMCMSpend 2+ hourson a problemthat turns out tobe one line ofcodework onanythingrelated toSalesforceapplicationssomeonerevokes anapprovalon your cryour codebreaksyourun into an issuewhile testingyour changeAFTERdeploying toproductionyour device isdeemednoncompliantforget toreset yourpasswordbefore itexpiresyou getsev2'd forfileuploadserviceyour ticketis blockedby legalCreate 3+COEs inone weekrestart yourmachinebecausechime "isn'tworking"yourconnectionsquestionseems a bittoo specificattend 6+hours ofmeetingsin one daycopied andpasted codefrom stackoverflow isCR approvedyou push achangethat breaksa pipelineyour crchangecausessev2your CRreceives6+ nitsyou getpagedafterhoursSolve aproblemthat youcreatedMake 6+revisionsfor yourCRyourchangeset failsvalidationyou getpaged ontheweekendHave 5+reviews ofyourdesign docrollbackproductionabortanMCMSpend 2+ hourson a problemthat turns out tobe one line ofcodework onanythingrelated toSalesforceapplicationssomeonerevokes anapprovalon your cryour codebreaksyourun into an issuewhile testingyour changeAFTERdeploying toproductionyour device isdeemednoncompliantforget toreset yourpasswordbefore itexpiresyou getsev2'd forfileuploadserviceyour ticketis blockedby legal

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