This bingo card has a free space and 24 words: Excessive amount of System.Debug(), No checking collection emptiness before DML, Gigantic Flow instead of multiple Subflows, Multiple triggers on one sObject, Hard-coded ID, Hard-coding UI text instead of Custom Labels, Exactly 75% test coverage, SOQL without WHERE or LIMIT outside Batch, No assertions in Tests, Only catching general catch(Exception), Code in trigger instead of Trigger Handler, No Test data factory/builder, Public Read/Write OWDs, SOQLs in loop, Unjustified big number of Record Flows on one sObject, Getting IDs by loop instead of Map(records), DMLs in loop, No Fault Paths in Flows, Method with 100s 'i++' lines for fake code coverage, Calling Queueable in loop without control mechanism or logging, Nondescriptive variable names in Flow, No flags to deactivate trigger declaratively, Hard-coded authentication instead of using Named Credentail and Excessive lack of .startTest() and .stopTest().
SoR2's code (Evil side) | Week 1 and 2 Vocabulary | JS Bingo | Registration Bingo! | Release Bingo
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.
