A photon travelling between Alpha Centauri and Earth does not experience time it effectively arrives instantly. We as observers however will see that it took 4 years to make its journey. The idea of whether it's recent or not is irrelevant, it is all relative (to the photon it's recent, to us the light is 4 years old).
Or perhaps its just incredibly automated. I'm sure a civilization that advanced could at the very least automated the mining aspects, if not the actual construction.
They don't operate at the same level, so it's common that a project would utilise both. For instance Terraform can create your K8s cluster, that you then later use as a target to run your containers
I'm not an expert in this area by any means, but my understanding is that vaccines use dead viruses rather than live ones, and they need a particular amount over time. So this wouldn't allow the virus to be passed along by mosquito generations, and you obviously couldn't control the dose amount. So not sure how practical the idea would be.
I get the sentiment here, but I don't think it's strictly true. The way I look at new technology is that I need to know enough about it to either discount it, or choose to use it. So long as I know what I'm talking about when I tell a prospective employer that I advise not using technology X, then they typically understand that I have the knowledge to make that decision.
So your advise should be, learn about the latest tech trend, try it out, and then have an informed opinion.
Informed enough to talk (read bullshit) your way through an interview. Honestly though - think about all of things on your resume that you said you had experience with (when it more of a resume of hope and less of a CV of experience). Was it actual, working knowledge that was applicable to your professional career, or was it passing knowledge from that time you followed a few tutorials?
I don't ask that to denigrate you. I did it. Lots of my peers did it. It's part of this silly game we play for employment. We complain about needing to pad resumes to get our foot in the door, but when we get to make hiring decisions, we automatically bin resumes of students who only put knowledge of one language and a handful of basic tools.
Not disagreeing with the sentiment, but your point about high availability is not entirely accurate. It's 3 'containers' required, meaning that if you were using Kubernetes etc, then you can have multiple services be HA across 3 hosts. Uptime monitoring etc is just config built into the service deployable.
