restart yourmachinebecausechime "isn'tworking"abortanMCMyou getpagedafterhoursyourchangeset failsvalidationyou push achangethat breaksa pipelinesomeonerevokes anapprovalon your cryou getpaged ontheweekendrollbackproductionyour CRreceives6+ nitsyour ticketis blockedby legalcopied andpasted codefrom stackoverflow isCR approvedyou getsev2'd forfileuploadserviceforget toreset yourpasswordbefore itexpiresyour crchangecausessev2your device isdeemednoncompliantSpend 2+ hourson a problemthat turns out tobe one line ofcodeMake 6+revisionsfor yourCRHave 5+reviews ofyourdesign docrun into an issuewhile testingyour changeAFTERdeploying toproductionyour codebreaksyouattend 6+hours ofmeetingsin one daySolve aproblemthat youcreatedwork onanythingrelated toSalesforceapplicationsyourconnectionsquestionseems a bittoo specificCreate 3+COEs inone weekrestart yourmachinebecausechime "isn'tworking"abortanMCMyou getpagedafterhoursyourchangeset failsvalidationyou push achangethat breaksa pipelinesomeonerevokes anapprovalon your cryou getpaged ontheweekendrollbackproductionyour CRreceives6+ nitsyour ticketis blockedby legalcopied andpasted codefrom stackoverflow isCR approvedyou getsev2'd forfileuploadserviceforget toreset yourpasswordbefore itexpiresyour crchangecausessev2your device isdeemednoncompliantSpend 2+ hourson a problemthat turns out tobe one line ofcodeMake 6+revisionsfor yourCRHave 5+reviews ofyourdesign docrun into an issuewhile testingyour changeAFTERdeploying toproductionyour codebreaksyouattend 6+hours ofmeetingsin one daySolve aproblemthat youcreatedwork onanythingrelated toSalesforceapplicationsyourconnectionsquestionseems a bittoo specificCreate 3+COEs inone week

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