Applying NASA coding guidelines to JavaScript or airspace is closer than you may think
summary
Claims that JPL/NASA C coding rules can raise JavaScript reliability by applying ten concrete rules: small functions, predictable control flow, no dynamic allocation at runtime, fixed-loop bounds, runtime assertions, minimal scope, parameter validation, limited transpiler use, short reference chains, and treat projects as critical from day one. Shows tools and measures: Chrome DevTools heap snapshots with a three-snapshot leak test, object pool to avoid GC churn, ESLint plugins and SonarQube metrics, bundle/perf comparisons for Babel, and a working artificial horizon flight at 1000m built with HTML/CSS/JS.
AI-written summary · about
chapters (15)
- 0:00Introduction and motivation
- 7:22Why JavaScript for aircraft instruments
- 12:26NASA coding guidelines overview
- 14:33Rule 1: Small functions
- 16:38Rule 2: Predictable control flow
- 18:43Rule 3: Memory management
- 25:56Rule 4: Fixed loop bounds
- 26:17Rule 5: Assertion density
- 27:23Rule 6: Minimal scope
- 28:10Rule 7: Input validation
- 28:51Rule 8: Preprocessor limits
- 30:38Rule 9: Pointer restrictions
- 31:43Rule 10: Critical mindset
- 32:45Applying guidelines in practice
- 33:29Conclusion and call to action
related talks
33mApplying NASA Coding Guidel ines to Java Script
58mImproving the Quality of JavaScript Code
36mEnforcing coding standards in a JS library
58mImproving Quality of JavaScript Code
38mJavascript Considered...Useful
40mJavaScript ... for Science!
06mJavaScript: The Fairly Odd Parts
46mInvisible performance. How fast is your JavaScript code?
