This bingo card has a free space and 24 words: Excessive amount of System.Debug(), Checking collection emptiness before DML, Gigantic Flow instead of multiple Subflows, Multiple triggers on one sObject, Hard-coded ID, All classes in without sharing mode, Exactly 75% test coverage, SOQLs without WHERE or LIMIT outside Batch, No assertions in Tests, Only catching general Exception in try-catch, Code in trigger instead of Trigger Handler, No test data factory or builder, Public Read/Write OWDs, DMLs in loop, Multiple Record Triggered Flows on same OperationType on one sObject, Getting IDs by loop instead of Map(records), SOQLs in loop, No Fault Paths in Flows, Missing bulk tests in test classes, Using Profiles instead of Permission Sets, Non‑descriptive variable names in Flow, No flags to deactivate trigger and validation rules declaratively, Hard-coded authentication instead of using Named Credentials and Excessive lack of .startTest() and .stopTest().
Salesforce Development Practices Bingo | JS Bingo | Red Ranks Bingo | Modifications | Bridges to Success: Listen for the answers and win a prize!
Share this URL with your players:
For more control of your online game, create a clone of this card first.
Learn how to conduct a bingo game.
With players vying for a you'll have to call about __ items before someone wins. There's a __% chance that a lucky player would win after calling __ items.
Tip: If you want your game to last longer (on average), add more unique words/images to it.
