JavaScript Coding Guidelines
•
1 like•727 views
This presentation has been prepared by Oleksii Prohonnyi for internal JS team meeting for improving skills of developers.
Recommended
More Related Content
What's hot
Viewers also liked
Similar to JavaScript Coding Guidelines
Similar to JavaScript Coding Guidelines (20)
More from Oleksii Prohonnyi
More from Oleksii Prohonnyi (20)
Recently uploaded
Recently uploaded (20)
JavaScript Coding Guidelines
- 1. JAVASCRIPT CODING GUIDELINES _by Oleksii Prohonnyi
- 4. Use === Instead of == "If two operands are of the same type and value, then === produces true and !== produces false.“ - JavaScript: The Good Parts
- 5. Eval = Bad Not only will this decrease your script's performance substantially, but it also poses a huge security risk.
- 6. Don't Use Short-Hand This is a terrible practice that should be avoided at all costs.
- 8. Declarations on Top It is a good coding practice to put all declarations at the top of each script or function.
- 9. Initialize Variables It is a good coding practice to initialize variables when you declare them.
- 11. Use shortcut declarations - Use {} instead of new Object() - Use "" instead of new String() - Use 0 instead of new Number() - Use false instead of new Boolean() - Use [] instead of new Array() - Use /()/ instead of new RegExp() - Use function (){} instead of new function()
- 12. Avoid Global Variables Minimize the use of global variables. This includes all data types, objects, and functions. Global variables and functions can be overwritten by other scripts. Use local variables instead, and learn how to use closures.
- 14. Always Declare Local Variables All variables used in a function should be declared as local variables. Local variables must be declared with the “var” keyword, otherwise they will become global variables.
- 15. Long List of Variables? Omit the "Var" Keyword and Use Commas Instead
- 17. Say “No!” to loops declarations Do not declare variables inside loops, don't make the engine work any harder than it must.
- 19. End Your Switches with Defaults Always end your switch statements with a default. Even if you think there is no need for it.
- 20. Avoid Cluttering The Global Namespace Using globals may cause naming conflicts between javascript source files and cause code to break. For this reason, it is a good practice to encapsulate functionality within a single global namespace.
- 21. Avoid sync "Ajax" calls If you think that your situation requires sync mode, it is most likely time to re-think your design. Very few (if any) situations actually require Ajax requests in sync mode.
- 22. Use JSON When storing data structures as plain text or sending/retrieving data structures via Ajax, use JSON instead of XML when possible.
- 23. Comment Your Code Always comment important sections of your code.
- 25. JAVASCRIPT OOD
- 26. Object Objects can be created using a constructor or an object literal. The constructor should be a custom function only.
- 28. Constructor Constructor functions simply assign values to slots of a newly created object.
- 30. Inheritance JavaScript supports inheritance hierarchies through prototyping in the manner of Self.
- 32. Encapsulation Encapsulation includes the idea that the data of an object should not be directly exposed.
- 34. CODE CONVENTION
- 35. Always follow team’s code convention!
- 36. REFERENCES
- 37. 1. “Clean Code: A Handbook of Agile Software Craftsmanship” (Robert Martin) 2. “Even Faster Web Sites” (Steve Souders) 3. “Maintainable JavaScript” (Nicholas Zakas) 4. w3schools.com 5. javascripttoolbox.com 6. tutsplus.com
- 38. SIGMA UKRAINE38