Archive
Software Agility
-
Avoid long ‘if/else if’ chains that could be replaced by a ‘switch’ statement
For code readability purpose, prefer using switch if there are three or more options in a if.
-
Avoid useless overriding method
Overring methods is a very powerfull way of factoring the code and produce complete fonctionnalities. However useless overriding methods can be a problem for…
-
The code contains too many uppercase control structure keywords
THE CODE CONTAINS TOO MANY UPPERCASE CONTROL STRUCTURE KEYWORDS
-
The code contains too many functions not complying with naming conventions
Complying with naming conventions make the source code easier to ready and so to maintain. Function names should start with an upper case and…
-
The code contains too many class names that do not begin with an uppercase letter
Complying with naming conventions make the source code easier to ready and so to maintain. Class names should start with an upper case.
-
Prefer to use an expression body for functions whose body consists of a single expression
Prefer using an expression body for functions with the body consisting of a single expression.
-
Use short variable declarations (:=) for variables with default values
Short variable declarations (:=) should be used if a variable is being set to some value explicitly.
-
Avoid naming unused receivers
If the receiver of a method is unused, do not give it a name. It’s more readable because it’s clear that the receiver is…