Commentthat doesn'treally explainthe codeCoverageyogaopportunityCodecomplexity> 155 deepmemberaccess toa structureCode thatshould reallyhave acomment butdoesn'tIncorrectrequirementtagRandomlycommentedout codeDLS2naming thatwouldnormally failstandards"//"commentDLS2namingthat leavesout the 2Link 2000+or FANS 1/Alogic thatshould bepostponedUnusedfunctionor fileFunctionthat couldbe staticbut isn'tRepeatedcode thatcould be afunction/macroGTC/GDUrequirementCode thatshould reallyhave arequirementOrphanedrequirementtag"Business"LogicwithinCDPTypowithin acommentUsage ofATN inreference toLink 2000+Commentthat liesDemo modefunctionalitythat shouldonly beKiosksCodingstandardsviolation"ToDo"commentVariablename withno vowelsNumber thatshould reallybe a defineorenumerationIncorrectlogic/bugCommentthat doesn'treally explainthe codeCoverageyogaopportunityCodecomplexity> 155 deepmemberaccess toa structureCode thatshould reallyhave acomment butdoesn'tIncorrectrequirementtagRandomlycommentedout codeDLS2naming thatwouldnormally failstandards"//"commentDLS2namingthat leavesout the 2Link 2000+or FANS 1/Alogic thatshould bepostponedUnusedfunctionor fileFunctionthat couldbe staticbut isn'tRepeatedcode thatcould be afunction/macroGTC/GDUrequirementCode thatshould reallyhave arequirementOrphanedrequirementtag"Business"LogicwithinCDPTypowithin acommentUsage ofATN inreference toLink 2000+Commentthat liesDemo modefunctionalitythat shouldonly beKiosksCodingstandardsviolation"ToDo"commentVariablename withno vowelsNumber thatshould reallybe a defineorenumerationIncorrectlogic/bug

FAA Data Comm Review 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
26
27
  1. Comment that doesn't really explain the code
  2. Coverage yoga opportunity
  3. Code complexity > 15
  4. 5 deep member access to a structure
  5. Code that should really have a comment but doesn't
  6. Incorrect requirement tag
  7. Randomly commented out code
  8. DLS2 naming that would normally fail standards
  9. "//" comment
  10. DLS2 naming that leaves out the 2
  11. Link 2000+ or FANS 1/A logic that should be postponed
  12. Unused function or file
  13. Function that could be static but isn't
  14. Repeated code that could be a function/macro
  15. GTC/GDU requirement
  16. Code that should really have a requirement
  17. Orphaned requirement tag
  18. "Business" Logic within CDP
  19. Typo within a comment
  20. Usage of ATN in reference to Link 2000+
  21. Comment that lies
  22. Demo mode functionality that should only be Kiosks
  23. Coding standards violation
  24. "ToDo" comment
  25. Variable name with no vowels
  26. Number that should really be a define or enumeration
  27. Incorrect logic/bug