Solve aproblemthat youcreatedyour CRreceives6+ nitsCreate 3+COEs inone weekMake 6+revisionsfor yourCRyou push achangethat breaksa pipelineabortanMCMwork onanythingrelated toSalesforceapplicationsyour ticketis blockedby legalsomeonerevokes anapprovalon your crforget toreset yourpasswordbefore itexpiresrestart yourmachinebecausechime "isn'tworking"your crchangecausessev2yourconnectionsquestionseems a bittoo specificyou getpagedafterhoursrollbackproductionyou getsev2'd forfileuploadserviceattend 6+hours ofmeetingsin one daySpend 2+ hourson a problemthat turns out tobe one line ofcodeyour device isdeemednoncompliantrun into an issuewhile testingyour changeAFTERdeploying toproductionHave 5+reviews ofyourdesign docyou getpaged ontheweekendyourchangeset failsvalidationyour codebreaksyoucopied andpasted codefrom stackoverflow isCR approvedSolve aproblemthat youcreatedyour CRreceives6+ nitsCreate 3+COEs inone weekMake 6+revisionsfor yourCRyou push achangethat breaksa pipelineabortanMCMwork onanythingrelated toSalesforceapplicationsyour ticketis blockedby legalsomeonerevokes anapprovalon your crforget toreset yourpasswordbefore itexpiresrestart yourmachinebecausechime "isn'tworking"your crchangecausessev2yourconnectionsquestionseems a bittoo specificyou getpagedafterhoursrollbackproductionyou getsev2'd forfileuploadserviceattend 6+hours ofmeetingsin one daySpend 2+ hourson a problemthat turns out tobe one line ofcodeyour device isdeemednoncompliantrun into an issuewhile testingyour changeAFTERdeploying toproductionHave 5+reviews ofyourdesign docyou getpaged ontheweekendyourchangeset failsvalidationyour codebreaksyoucopied 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. Solve a problem that you created
  2. your CR receives 6+ nits
  3. Create 3+ COEs in one week
  4. Make 6+ revisions for your CR
  5. you push a change that breaks a pipeline
  6. abort an MCM
  7. work on anything related to Salesforce applications
  8. your ticket is blocked by legal
  9. someone revokes an approval on your cr
  10. forget to reset your password before it expires
  11. restart your machine because chime "isn't working"
  12. your cr change causes sev2
  13. your connections question seems a bit too specific
  14. you get paged after hours
  15. rollback production
  16. you get sev2'd for fileupload service
  17. attend 6+ hours of meetings in one day
  18. Spend 2+ hours on a problem that turns out to be one line of code
  19. your device is deemed noncompliant
  20. run into an issue while testing your change AFTER deploying to production
  21. Have 5+ reviews of your design doc
  22. you get paged on the weekend
  23. your change set fails validation
  24. your code breaks you
  25. copied and pasted code from stack overflow is CR approved