attend 6+hours ofmeetingsin one dayrestart yourmachinebecausechime "isn'tworking"your crchangecausessev2copied andpasted codefrom stackoverflow isCR approvedyour CRreceives6+ nitssomeonerevokes anapprovalon your crMake 6+revisionsfor yourCRwork onanythingrelated toSalesforceapplicationsyourconnectionsquestionseems a bittoo specificyou getsev2'd forfileuploadserviceSpend 2+ hourson a problemthat turns out tobe one line ofcodeyou getpaged ontheweekendCreate 3+COEs inone weekyou push achangethat breaksa pipelineSolve aproblemthat youcreatedabortanMCMyour device isdeemednoncompliantrun into an issuewhile testingyour changeAFTERdeploying toproductionyou getpagedafterhoursrollbackproductionyourchangeset failsvalidationHave 5+reviews ofyourdesign docyour codebreaksyouyour ticketis blockedby legalforget toreset yourpasswordbefore itexpiresattend 6+hours ofmeetingsin one dayrestart yourmachinebecausechime "isn'tworking"your crchangecausessev2copied andpasted codefrom stackoverflow isCR approvedyour CRreceives6+ nitssomeonerevokes anapprovalon your crMake 6+revisionsfor yourCRwork onanythingrelated toSalesforceapplicationsyourconnectionsquestionseems a bittoo specificyou getsev2'd forfileuploadserviceSpend 2+ hourson a problemthat turns out tobe one line ofcodeyou getpaged ontheweekendCreate 3+COEs inone weekyou push achangethat breaksa pipelineSolve aproblemthat youcreatedabortanMCMyour device isdeemednoncompliantrun into an issuewhile testingyour changeAFTERdeploying toproductionyou getpagedafterhoursrollbackproductionyourchangeset failsvalidationHave 5+reviews ofyourdesign docyour codebreaksyouyour ticketis blockedby legalforget toreset yourpasswordbefore itexpires

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