~/talk

Applying NASA coding guidelines to JavaScript or airspace is closer than you may think

slides:none on file

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

  1. 0:00Introduction and motivation
  2. 7:22Why JavaScript for aircraft instruments
  3. 12:26NASA coding guidelines overview
  4. 14:33Rule 1: Small functions
  5. 16:38Rule 2: Predictable control flow
  6. 18:43Rule 3: Memory management
  7. 25:56Rule 4: Fixed loop bounds
  8. 26:17Rule 5: Assertion density
  9. 27:23Rule 6: Minimal scope
  10. 28:10Rule 7: Input validation
  11. 28:51Rule 8: Preprocessor limits
  12. 30:38Rule 9: Pointer restrictions
  13. 31:43Rule 10: Critical mindset
  14. 32:45Applying guidelines in practice
  15. 33:29Conclusion and call to action
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.