gaspersic/freeCodeCamp
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed Grammer (#27349)

Browse Source 
I used a better word for the sentence.
This commit is contained in:
Conela
2019-01-14 19:23:47 -05:00
committed by Tom
parent 672e00b2f4
commit f3630a6d34
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
guide/english/agile/code-smells/index.md
View File

@ -12,7 +12,7 @@ It is important to understand that smelly code works, but is not of good quality
2. Large classes - Classes having too many lines of code. This may indicate that the class is trying to do too many things, and needs to be broken up into smaller classes.
3. [Magic numbers](https://en.wikipedia.org/wiki/Magic_number_(programming)) - Variables (or `if` statements) scattered in the code that hold numeric values with no apparent meaning.
4. Many-parameter methods - Methods that take more that 2 or 3 parameters usually indicate that the method does more than one thing and should be broken down to multiple methods.
5. Unclear method or variable naming - A programmer should be able to understand what a method does without looking at the method's body. If the name or the parameter naming is vague, it is an indicator that the method should be refactored to reveal its purpose in the code.
5. Unclear method or variable naming - A programmer should be able to understand what a method does without looking at the method's body. If the name or the parameter naming is indistinct, it is an indicator that the method should be refactored to reveal its purpose in the code.
#### More Information:
* _Refactoring: Improving the Design of Existing Code - Kent Beck, Martin Fowler_