Completed
Do one thing Long functions: less readable, not reusable, harder to test, harder to reactor
Class Central Classrooms beta
YouTube videos curated by Class Central.
Classroom Contents
Applying NASA Coding Standards to JavaScript
Automatically move to the next video in the Classroom when playback concludes
- 1 Intro
- 2 Unification - effective method to decrease diversity. Aim for unification is to place elements in particular order building strict system which is comfortable to use.
- 3 The same works for engineering Unification never stops
- 4 Unification Decreases development cost standardizing development flow and technologies stack
- 5 Do one thing Long functions: less readable, not reusable, harder to test, harder to reactor
- 6 Predictability • If you want to write reliable code-drop to write cool one and write predictable • Define coding standard and follow it . Use static analysis to support standard and reduce chance for…
- 7 Do not use dynamic memory allocation after initialization
- 8 Test well • Higher tests density is less defects you get • Minimal amount of tests is 2 per function • Watch for anomalies in system state during run time. Generate and handle errors in case of criti…
- 9 Data objects must be declared at the smallest possible level of scope
- 10 The return value of non-void functions must be checked by each calling function, and the validity of parameters must be checked inside each function
- 11 The use of pointers should be restricted. Specifically, no more than one level of dereferencing is allowed. Function pointers are not permitted
- 12 All code must be compiled, from the first day of development, with all compiler warnings enabled
- 13 If red? Do not panic. Simply, prioritize, refactor and add tests piece by piece.
