Applying NASA Coding Guidel ines to Java Script
summary
Applies JPL/NASA coding rules to JavaScript and shows a working HTML/JS JavaScript aircraft instrument that actually flew over Amsterdam at ~1,000 m for several minutes without failure. Claims: follow short functions, simple control flow, fixed-loop bounds, two assertions per function (runtime assertions + unit tests), smallest possible scope, check return values, limit transpilation/bundling. Practices shown: ESLint on hooks, TypeScript for types, devtools memory profiling, object pooling, cleaning listeners; result: prototype works and highlights reliability gains.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:12Unification in software
- 6:43JavaScript for aircraft instruments
- 10:37NASA coding guidelines overview
- 12:04Rule one keep functions short
- 13:33Rule two control flow predictability
- 15:21Rule three respect memory
- 19:14Rule four fixed loop bounds
- 19:34Rule five test assertions
- 21:19Rule six minimize shared state
- 22:06Rule seven validate returns
- 23:09Bundling performance impact
- 25:44Rule nine restrict pointers
- 27:18Test from day one
- 29:54Future of JavaScript in serious systems
- 30:17Q&A on code comments
related talks
35mApplying NASA coding guidelines to JavaScript or airspace is closer than you may think
06mJavaScript: The Fairly Odd Parts
38mJavascript Considered...Useful
58mImproving Quality of JavaScript Code
58mImproving the Quality of JavaScript Code
40mJavaScript ... for Science!
12mThe Goodness of JavaScript
44mJavaScript is weird. MythBusters special.