abortanMCMyour CRreceives6+ nitsMake 6+revisionsfor yourCRrestart yourmachinebecausechime "isn'tworking"attend 6+hours ofmeetingsin one dayyou getpaged ontheweekendyourconnectionsquestionseems a bittoo specificyour device isdeemednoncompliantyour ticketis blockedby legalsomeonerevokes anapprovalon your cryou getsev2'd forfileuploadservicerollbackproductionwork onanythingrelated toSalesforceapplicationsyourchangeset failsvalidationCreate 3+COEs inone weekrun into an issuewhile testingyour changeAFTERdeploying toproductionyou getpagedafterhoursyour crchangecausessev2forget toreset yourpasswordbefore itexpiresSpend 2+ hourson a problemthat turns out tobe one line ofcodeSolve aproblemthat youcreatedcopied andpasted codefrom stackoverflow isCR approvedyour codebreaksyouHave 5+reviews ofyourdesign docyou push achangethat breaksa pipelineabortanMCMyour CRreceives6+ nitsMake 6+revisionsfor yourCRrestart yourmachinebecausechime "isn'tworking"attend 6+hours ofmeetingsin one dayyou getpaged ontheweekendyourconnectionsquestionseems a bittoo specificyour device isdeemednoncompliantyour ticketis blockedby legalsomeonerevokes anapprovalon your cryou getsev2'd forfileuploadservicerollbackproductionwork onanythingrelated toSalesforceapplicationsyourchangeset failsvalidationCreate 3+COEs inone weekrun into an issuewhile testingyour changeAFTERdeploying toproductionyou getpagedafterhoursyour crchangecausessev2forget toreset yourpasswordbefore itexpiresSpend 2+ hourson a problemthat turns out tobe one line ofcodeSolve aproblemthat youcreatedcopied andpasted codefrom stackoverflow isCR approvedyour codebreaksyouHave 5+reviews ofyourdesign docyou push achangethat breaksa pipeline

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