Therefore the need to rely on data to find more objectivity when debating public policies. Yes data can be twisted and most of the time is poorly reported and interpreted by people, but it's better than relying on personal anecdotes.
1,488 karma · joined April 7, 2017
www.benoitrostykus.com
Therefore the need to rely on data to find more objectivity when debating public policies. Yes data can be twisted and most of the time is poorly reported and interpreted by people, but it's better than relying on personal anecdotes.
Less than 1% of their funding is from the government.
Tesla received billions in government subsidies... Is it state-affiliated?
There doesn't need to be. When they run AB tests, it's possible that they'd pick the winning cell if it makes the Elon metrics look better.
Even if the algorithm doesn't do anything explicit about boosting him, it can be tweaked through AB testing to favor him.
It doesn't have to be in the algorithm for the systems to be tweaked to please Elon vanity metrics.
[I've been running lots of ML AB tests over the years, some in organizations of similar size & complexity as Twitter]
On a more controversial note, I trust more Meta & Google engineers proposing alternative schedulers that have been properly AB tested on millions of servers running a wide range of heterogeneous software VS small-scale synthetic benchmarks even when run by experts/maintainers.
[1]: https://lwn.net/ml/linux-kernel/20221130082313.3241517-1-tj@...
> real free market environment
I'm hoping you're just kidding.
I'm not super familiar with ChatGPT internals, but there are plenty of ways to tack on uncertainty estimates to predictions of typical "large scale ML models" without touching Bayesian stuff (which only work for small scale academics problems). You can do simple parametric posteriors estimation or if all you have is infinite compute and don't even want to bother with anything "mathy", bootstrapping is the "scalable / easy" solution.
Right. If your AUC is in the 90's you usually either have a bug, or a predictive task that isn't very challenging.
I am of the opposite sentiment. I think it would do wonders. It's very easy in a mega-corp to completely lose track of what the product is, who the customers are. And my intuition is that most VPs at mega-corps think about products in the abstract and focus more on politics & empire building/strategy than actually caring about the customers - and it definitely shows for companies like Google.
Just last week I tried to spawn a GPU instance on GCP, and despite being very familiar with the space (I work on cloud infra), after 20 minutes of fighting the overly complex UI and ridiculously broken flows, I still hadn't my instance up. In the next 3 minutes, I signed up for Lambda Labs, entered a CC, clicked a single button and ssh'ed into my VM.
That's what any start-up focuses on: the product. And that's why they always win over bloated mega-corps focused on internal processes and infighting, whose employees self-select for being complacent about mediocre products as long as the monopoly keeps printing fat paychecks.
I must say that's one of the most unorthodox description of what a company does I've seen.
How is a bread factory or a plumber "turning risk into money"? It sounds like you're describing an insurance company or a bank, not, you know a company like Google who produces free software & services to billions of people in exchange for monetizing their attention. Focusing on risk mitigation in a company is explicitly optimizing for protecting existing income stream at the expense of innovation, customers, and new income streams. It's not what "any company does": it's what uninspired companies who have lost their ways focus on.
It sounds like what a consultant used to "financialize" everything would say to solve Google's problems and slowly turn it into an intangible conglomerate like GE who is just the shadow of its previous self. But maybe this time has arrived for Google?
Mainstream schedulers make no distinction between service & batch jobs out of the box - you need to explicitly go out of your way to implement differential preferences when it comes to scheduling latency for example.
I am surprised cost isn't a concern for you guys, I actually had assumed you went all in on bin-packing+firecracker oversubscription to maximize your margin.
IMO it's one of the better part of k8s. The core scheduler is pretty well written and extensible through scheduling plugins, to implement whatever policies you heart desires (which we extensively make use of at Netflix).
The main issue I have with it is the lack of built-in observability, which makes it non-trivial to A/B test scheduling policies in large scale deployment setups because you want to be able to log the various subscores of your plugins. But it's so extensible through NodeAffinity and PodAffinity plugins that you can even delegate part (or all!) of the scheduling decisions outside of it if you want.
Besides observability, one issue we've had to overcome with k8s scheduling is the inheritance of the Borg design decisions around pod shape immutability, which makes implementing things like oversubscription less easy in a "native" way.
No one, that's my point. If academia has not taught to the author that his intelligence isn't unusual, the workforce of his new employer certainly will. Listing github stars and twitter followers in the second paragraph as an achievement to me transpires lack of maturity and a need for external validation. On the bright side, being good at self-promotion when entering a mega-corporation will make sure he has a great career in front of him.
Promoting the non-enforcement of the law is both immoral and erodes the foundations of a civilized society.