adding memory: $xxx per missile paying a software engineer to fix a memory leak: $x,xxx,xxx
Paying the software engineer would be a fraction of the cost to fix the memory leak in software. Recertification of the software would blow it all away.
It seems like those shouldn't be coupled, but I seem to remember (horror) stories about programs running on machines with segmented memory, where the segments straddled each other, and/or where the last segment wrapped around to the beginning of RAM. Expanding RAM in such a scenario would cause wrapped writes to no longer wrap, for example.
Or any other illogical reason a program could use or abuse the size of RAM for. It just never ceases to amaze me how things that should be completely decoupled can end up not being.
> blow it all away
I appreciated the wording there. :)
This makes me wonder, will self-driving cars need recertification if even one line of code is touched?