I have a constructive recommendation for you and your engineering management for future cases such as this.
First, when some team says "we want to use helm and etcd for some reason and we haven't been able to figure out how to get that working on our existing platform," start by asking them what their actual goal is. It is obscenely unlikely that helm (of all things) is a fundamental requirement to their work. Installing temporal, for example, doesn't require helm and is actually simple, if it turns out that temporal is the best workflow orchestrator for the job and that none of the probably 590 other options will do.
Second, once you have figured out what the actual goal is, and have a buffet of options available, price them out. Doing some napkin math on how many people were involved and how much work had to go into it, it looks to me that what you have spent to completely rearchitect your stack and operations and retrain everyone -- completely discounting opportunity cost -- is likely not to break even in even my most generous estimate of increased productivity for about five years. More likely, the increased cost of the platform switch, the lack of likely actual velocity accrual, and the opportunity cost make this a net-net bad move except for the resumes of all of those involved.
There are also serious physical constraints. Most office buildings were not designed to have the number of bathrooms that subdividing into an apartment complex would require for example.
Not speaking for Alexa or Amazon, where I have worked in the past, but the wakeword detection is done separately in a much lower power, localized model using hardware features. On the downside this means that you can only select from a few wakewords and the filtering etc. are limited (e.g. the local model is not aware of commercials being played concurrently in the world, so has to wake up the bigger model, which can check to see if that's happening). On the positive side, it's much lower power and mitigates concerns that Alexa is listening to normal activity/conversations.
governments are providing you with safe, clean water, roadways, basic standards of food safety, protection from enemies, disaster prevention and relief, and social services beyond the feasible scope of charity. They may suck at many things, but existential risk (even if just civilizational shift owing to mass-produced disinformation) is a great place to point a government at.
Donald Trump and Fox News are maybe the canonical examples in modern times. Say what you like about Rupert Murdoch and Trump, they're incredibly effective communicators who have built fanatical religions based on words alone. And what we're about to see is that level of reach and intensity multiplied by millions.
I mean, unless you're one of the 75 million people who died in the massacres, the concentration camps, the firebombing, the disease, the starvation. Maybe we could find a way to have a great era without that, they might suggest.
With respect, I think 'people's priors all seem to be' is doing a lot of work there and forging new ground in both-sidesism. Man, who's to blame here, the self-dealing serial scam artist, eyeball print thief, crypto booster, and professional prevaricator, or the OpenAI board of, basically, politically naive and innocent academics?
if you have the ability to execute code on a CPU, and that CPU is connected to a bus, and that bus is connected to a network card, you can sniff traffic. If you have data and business processes that include at least one entity A that lacks absolute trust at least one other entity B in your cluster, then the visible traffic of A by B is bad.
'wall street and silicon valley', as if there weren't hundreds of millions of dark money billionaire slush funds and the world's biggest and most effective propaganda network in play.
remember when he published the actual algorithm for twitter and everyone could look at the code that was reportedly boosting the woke and canceling maga, and it turned out not to have any kind of censorship regime or boosting, except it boosted his account? That was a great time.
Incorrect, in most apps nontrivial content is highly personalized and dynamically served, auth in microservices is frequently two or more hop rather than one hop, and ad serving and metrics frequently involve synchronous steps.
it's not actually irrespective of architecture. Some architectures are significantly more prone to certain kinds of problems than others. For example, monoliths can become so large as to make development, especially many-team development, inconvenient or impossible. In the specific case of microservices, the key benefit (multiple teams can develop and deliver in parallel without stepping on each other, separating concerns into their own ownership areas) has the tradeoff of distributed systems overhead, which can range from high latency (when a number of microservices are in a serialized hot path and the complexity is not being effectively managed) to lowered availability or consistency (when data is radiating through a network of microservices asynchronously and different services 'see' different data and make conflicting correct decisions). Monoliths see this set of performance problems much, much later in their lifecycle, because they have much better data locality and local function call characteristics.
Incorrect. Frequently, UI lag on components that hit server side back services is made significantly worse by naïve microservices, especially in the face of organic growth.
Specifically, every API call that traverses a machine, boundary, necessarily impart, additional latency, and uncontrolled microservices can have a multiplicative effect
I guess I don't understand how a bunch of dead people resulting from the insurrection can be classified as anything other than dead. In what way do they not count? Does it excuse anything or make it ok if we parsed 'deadly' so narrowly as to not include the suicides and strokes?
Fundamentally you & yours don't want to say 'deadly' because it sounds bad. Guess what, it is! You own that.