Requires horizontal scrolling Non- searchable variable name Unpronounceable naming Use of pun Switch Statement Abuse Multiple Return Points Long Method Violates Command- Query Separation vertical openness between concepts variable declared far from its usage Message Chains – a.b().c().d() trainwreck Missing summary comment on a public method Comments Explaining Code Deep Nesting Confusing Naming Catching exceptions and logging only large functions with nested structures Too many arguments (>3) Error codes instead of exception missing legal comments Dependent functions are far apart Commented Out Code Code Duplication Too Many Responsibilities Requires horizontal scrolling Non- searchable variable name Unpronounceable naming Use of pun Switch Statement Abuse Multiple Return Points Long Method Violates Command- Query Separation vertical openness between concepts variable declared far from its usage Message Chains – a.b().c().d() trainwreck Missing summary comment on a public method Comments Explaining Code Deep Nesting Confusing Naming Catching exceptions and logging only large functions with nested structures Too many arguments (>3) Error codes instead of exception missing legal comments Dependent functions are far apart Commented Out Code Code Duplication Too Many Responsibilities
(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.
Requires horizontal scrolling
Non-searchable variable name
Unpronounceable naming
Use of pun
Switch Statement Abuse
Multiple Return Points
Long Method
Violates Command-Query Separation
vertical openness between concepts
variable declared far from its usage
Message Chains – a.b().c().d() trainwreck
Missing summary comment on a public method
Comments Explaining Code
Deep Nesting
Confusing Naming
Catching exceptions and logging only
large functions with nested structures
Too many arguments (>3)
Error codes instead of exception
missing legal comments
Dependent functions are far apart
Commented Out Code
Code Duplication
Too Many Responsibilities