your codebreaksyouwork onanythingrelated toSalesforceapplicationsSpend 2+ hourson a problemthat turns out tobe one line ofcodeCreate 3+COEs inone weekyou push achangethat breaksa pipelineyour device isdeemednoncompliantMake 6+revisionsfor yourCRabortanMCMyour CRreceives6+ nitsyou getpagedafterhoursHave 5+reviews ofyourdesign docattend 6+hours ofmeetingsin one dayyour crchangecausessev2restart yourmachinebecausechime "isn'tworking"forget toreset yourpasswordbefore itexpiresSolve aproblemthat youcreatedrollbackproductionsomeonerevokes anapprovalon your cryourconnectionsquestionseems a bittoo specificyour ticketis blockedby legalyou getsev2'd forfileuploadserviceyou getpaged ontheweekendrun into an issuewhile testingyour changeAFTERdeploying toproductionyourchangeset failsvalidationcopied andpasted codefrom stackoverflow isCR approvedyour codebreaksyouwork onanythingrelated toSalesforceapplicationsSpend 2+ hourson a problemthat turns out tobe one line ofcodeCreate 3+COEs inone weekyou push achangethat breaksa pipelineyour device isdeemednoncompliantMake 6+revisionsfor yourCRabortanMCMyour CRreceives6+ nitsyou getpagedafterhoursHave 5+reviews ofyourdesign docattend 6+hours ofmeetingsin one dayyour crchangecausessev2restart yourmachinebecausechime "isn'tworking"forget toreset yourpasswordbefore itexpiresSolve aproblemthat youcreatedrollbackproductionsomeonerevokes anapprovalon your cryourconnectionsquestionseems a bittoo specificyour ticketis blockedby legalyou getsev2'd forfileuploadserviceyou getpaged ontheweekendrun into an issuewhile testingyour changeAFTERdeploying toproductionyourchangeset failsvalidationcopied andpasted codefrom stackoverflow isCR approved

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