jeena/en.javascript.info
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

up

Browse source
This commit is contained in:
Ilya Kantor 2017-01-18 09:53:11 +01:00
parent 6c9c2219ba
commit a7c00e1c76
14 changed files with 260 additions and 252 deletions
Download patch file Download diff file Expand all files Collapse all files

4
1-js/03-code-quality/02-coding-style/article.md
View file

@ -307,4 +307,6 @@ Also you can see [the manual](http://eslint.org/docs/user-guide/getting-started)
All syntax rules from this chapter and the style guides aim to increase readability.
When you read style guides and think about "how to write better", the sole criterion is "does the code become more readable and easier to understand?" Then it becomes easier to pick up the best practices for that. Or even abandon some in cases when you see that they don't help.
All of them are debatable.
When we think about "how to write better?", the sole criterion is "what makes the code more readable and easier to understand? what helps to evade errors?" The answer helps to pick up best practices. And maybe to abandon some in case if they don't contribute.