Readit NewsNo discussion of route53 profiles. More importantly it doesn’t seem to make the connection with GCP’a excellent implementation of projects and AWS’s half convoluted answer RAM (although they have started to address this with projects in Unified Studio).
1) Palantir was the first breath of fresh air that brought actually good tech with modern tech support practices to the warfighter, and by extension put the big defense contractors on notice. I personally believe this impact was tremendously important as there were real safety connotations involved, and anyone with a family member downrange could appreciate this.
2) Palantir was great targeting software that worked like modern tech vs a custom Linux distro with a GUI from 1970 and required 5 months of finagling to get vendor support for.
So Palantir just brought standard 2010’s tech to soldiers betting their safety on it. This was incredible although ordinary.
With the increasing standardization of application stacks, automation, AI (seems mostly just hype), companies are thinking even if they need developers in larger numbers they can most definitely do with cheaper offshore developers.
So US government, offshoring nation's government and American companies and their vendors are ironically on same page that H1B is going out. Even if they have different benefit or loss with current system.
In Europe, a Ford Transit is just what the local plumber or electrician drives. It's a no-nonsense work tool. In America, thanks to what I assume is decades of media tropes, the same van is portrayed as the getaway car in a heist or the “creepy unmarked van” parents warn their kids about.
It’s as if a hammer were seen as suspicious because it could be used in a crime.
For any job-hunters, it's important you forget this during interviews.
In the past I've made the mistake of trying to convey this in system design interviews.
Some hypothetical startup app
> Interviewer: "Well what about backpressure?"
>"That's not really worth considering for this amount of QPS"
> Interviewer: "Why wouldn't you use a queue here instead of a cron job?"
> "I don't think it's necessary for what this app is, but here's the tradeoffs."
> Interviewer: "How would you choose between sql and nosql db?"
> "Doesn't matter much. Whatever the team has most expertise in"
These are not the answers they're looking for. You want to fill the whiteboard with boxes and arrows until it looks like you've got Kubernetes managing your Kubernetes.
That becomes obvious when you start bootstrapping an HA cluster with multiple control plane nodes.
K8s is not for the faint of heart…or rational system designers ;)