Applying NASA coding standards to JavaScript

Re:Applying NASA coding standards to JavaScript by PixelsCommander on Thursday January 08, 2015 @09:47AM (#8856554)

"focus on more extensive automated testing, focus on more profiling, and focus on general software engineering principles like single-responsibility and DRY" - this is exactly what was suggested in article. Except may be DRY which is more about design.

[ Parent | on HN ]

Re:Applying NASA coding standards to JavaScript by worklogin on Thursday January 08, 2015 @10:01AM (#8856625)

sigh this is where HN gets its reputation.

Of course the article wasn't suggesting manual testing and avoid profiling, but it MOSTLY recommended techniques and tips that do not apply to the web. That's what jerf spent three paragraphs outlining.

[ Parent | on HN ]

Re:Applying NASA coding standards to JavaScript by jacquesm on Thursday January 08, 2015 @01:32PM (#8857965)

DRY is also very much about coding (cut-and-paste versus extraction of common code into functions).

[ Parent | on HN ]