Variable names is just documentation. Having types that can assert some condition on the underlying value is not even comparable to "having a named return variable". (just document? just name variables?) You don't care about what the name of the returned value is, you care about what *it is*.
What does this solve? Genuine question. You still have to manage connectivity, and synchronization. Also not so sure that stream reading will necessarily be quantized chunks of your updates sent from the server.
So.. For which company? The sentence "there are scam profiles all around the IT world" would not be on any real company of scale guidelines, and no company would put that much liability in one "slide" even if they had them.
Yes, many companies will cap out on the advancement ladder so that at that point there's no requirement to advance further formally. Any company doing up or out indefinitely will obviously just drop valuable resources. You can still advance in pay etc.
There are times when things truly change last minute, or new intel pops up. State that the new changes will require pushing the deadline, and if curious ask if they can tell more about how the changed requirements came about so that you have all the right context for the next iteration.
I think it's more that as the term is widely adopted via something like LLMs they convey different meaning to users of the tools branded by it. Since users and their perspective of "artificial intelligence" and its meaning have no relation to the original term from 50-70 years ago.