NASA writes mission-critical flight software in C.
And the rules are absolutely INSANE.
> No recursion. Ever.
> Every loop must have a provable upper bound.
> No dynamic memory allocation after initialization.
> Max ~60 lines per function.
> Minimum 2 assertions per function.
> Every return value must be checked.
> Zero compiler warnings allowed.
> Daily static analysis. Zero warnings there too.
> No function pointers.
> Restricted pointer dereferencing.
This is how they write code at NASA / JPL for mission-critical systems.
insane Claude Code setup.
instead of asking it to "mek app" like a total normie, you first let it spin up 1m subagents to simulate 10¹² branches of civilization from 4000 BC recursively to emulate in which universe a specific version of your app is going to be most successful
so we raised a new round, but haven't told anyone yet
our investors are like, hey put our money to use how come burn isn't going up
i gotchu fam
introducing burn rate by runway
an award winning, blind taste-tested (by me!) hot sauce, wrapped in a genuine $100 bill
for $13.99
@RhysSullivan I’ll never understand the parents that show up 1 or 2 hours early just to first in line…
Are they trying to get out earlier?
They really have nothing better to do?