@szescstopni @rrwo @Threadbane I've been writing code at professional level for most of my life. I can confirm that I've never used generators :)
My point was about the efficiency of code and how deeply it's tested against all possible use cases - such as "somebody at some point will tilt the antenna by a few degrees and we need a fallback mechanism to find earth again".
I don't feel like there's so much depth, throughout testing of all the possible things that can go wrong, and long-term thinking in the code we write today. The code we ship is often the result of trade-offs - like "we need to release it by this date, and it's ok to cut some corners, decrease test coverage, or have errors - as long as they're below this SLO".
And I'm talking of FAANG-level code, not of the small local startup.
At ESA and NASA maybe they still do things differently (I hope), but most of the commercial software is definitely far from the level of "you can run it for the next 50 years and more, and it'll just work".
Also, this whole masterpiece of engineering could fit into 69 KB of RAM. I can't think of a single non-trivial piece of code today that can fit into that size. It's like, as we added more resources, we just started using all of them to do the same things, rather than doing more things with more resources.
@blacklight @szescstopni @rrwo @Threadbane Don't worry, there's still microcontrollers, if you want to play with tiny RAM sizes! (though *some* are Gb+ of Flash, now)