Spend 2+ hourson a problemthat turns out tobe one line ofcoderestart yourmachinebecausechime "isn'tworking"someonerevokes anapprovalon your crSolve aproblemthat youcreatedyou getpagedafterhoursyour codebreaksyouyour CRreceives6+ nitsyou getsev2'd forfileuploadserviceCreate 3+COEs inone weekyou getpaged ontheweekendforget toreset yourpasswordbefore itexpiresyour device isdeemednoncompliantyour crchangecausessev2your ticketis blockedby legalattend 6+hours ofmeetingsin one dayrun into an issuewhile testingyour changeAFTERdeploying toproductionyourconnectionsquestionseems a bittoo specificwork onanythingrelated toSalesforceapplicationsMake 6+revisionsfor yourCRrollbackproductionabortanMCMyourchangeset failsvalidationHave 5+reviews ofyourdesign doccopied andpasted codefrom stackoverflow isCR approvedyou push achangethat breaksa pipelineSpend 2+ hourson a problemthat turns out tobe one line ofcoderestart yourmachinebecausechime "isn'tworking"someonerevokes anapprovalon your crSolve aproblemthat youcreatedyou getpagedafterhoursyour codebreaksyouyour CRreceives6+ nitsyou getsev2'd forfileuploadserviceCreate 3+COEs inone weekyou getpaged ontheweekendforget toreset yourpasswordbefore itexpiresyour device isdeemednoncompliantyour crchangecausessev2your ticketis blockedby legalattend 6+hours ofmeetingsin one dayrun into an issuewhile testingyour changeAFTERdeploying toproductionyourconnectionsquestionseems a bittoo specificwork onanythingrelated toSalesforceapplicationsMake 6+revisionsfor yourCRrollbackproductionabortanMCMyourchangeset failsvalidationHave 5+reviews ofyourdesign doccopied andpasted codefrom stackoverflow isCR approvedyou 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. Spend 2+ hours on a problem that turns out to be one line of code
  2. restart your machine because chime "isn't working"
  3. someone revokes an approval on your cr
  4. Solve a problem that you created
  5. you get paged after hours
  6. your code breaks you
  7. your CR receives 6+ nits
  8. you get sev2'd for fileupload service
  9. Create 3+ COEs in one week
  10. you get paged on the weekend
  11. forget to reset your password before it expires
  12. your device is deemed noncompliant
  13. your cr change causes sev2
  14. your ticket is blocked by legal
  15. attend 6+ hours of meetings in one day
  16. run into an issue while testing your change AFTER deploying to production
  17. your connections question seems a bit too specific
  18. work on anything related to Salesforce applications
  19. Make 6+ revisions for your CR
  20. rollback production
  21. abort an MCM
  22. your change set fails validation
  23. Have 5+ reviews of your design doc
  24. copied and pasted code from stack overflow is CR approved
  25. you push a change that breaks a pipeline