Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Code quality: Non meaningful identifiers #10

Closed
s4rify opened this issue Oct 29, 2020 · 0 comments
Closed

Code quality: Non meaningful identifiers #10

s4rify opened this issue Oct 29, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@s4rify
Copy link
Collaborator

s4rify commented Oct 29, 2020

Many names of variables and functions are chosen in a way, that it takes longer to recognize which tasks and contents they represent.
Example: A file name is stored in variables "temp" and "convertedValue". Other identifiers were "arr" and "arr2" and "i" and "i2".

Disadvantage 1: Understanding and changing the code causes more effort, because one has to go on "treasure hunt" again and again to trace back what is actually written into a variable.

Disadvantage 2: Risk of errors: Two not meaningful variables from the same type can be confused. Who knows what is in "i" and what is in "i2" if the variables were described at a remote code location?

@s4rify s4rify added the enhancement New feature or request label Oct 29, 2020
@s4rify s4rify closed this as completed Nov 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant