Archive
Michael MULLER
-
The code contains too many instructions that initialize zones of data with zeros or spaces
For code readability purpose, avoid initializations with 0 or spaces.
-
The code contains too many data contigus levels
When creating a new data level, do not add 1 to the previous level. Having not contigus level is easier for inserting an intermediate…
-
The code contains too many back performs
For readability purpose, avoid using perform with a paragraph higher in the code.
-
The code contains too many dangerous usage patterns in file management
Avoid dangerous file usage patterns. File management contains dangerous usage patterns.
-
The code contains paragraphs having the same name
Paragraphs having the same name is ambigous, and should be strongly avoided.
-
The code contains too many bad area A usages
In a cobol file, area A (the first four columns) are reserved for divions, sections names, paragraph names and level 01 data declaration.
-
Optional property declarations should use ‘?’ syntax
In TypeScript there are several ways to declare an optional property, i.e. a property which might be missing from an object: adding “| undefined”…
-
Errors should not be created without being thrown
Creating a new Error without actually throwing it is useless and is probably due to a mistake.
-
Avoid explicit type when it can be inferred from literal value affected
For code readability purpose, if a property initializer is a scalar value or the return type can be clearly inferred from the body then…
-
Avoid structures initializations with unamed fields
You should almost always specify field names when initializing structs. This is now enforced by go vet.