I think that a lot of very basic LLM use cases come down to articulating your need. If you're not the sort of person who's highly articulate, this is likely to be difficult for you.
I'm personally in the habit of answering even slightly complex questions by first establishing shared context - that is, I very carefully ensure that my conversational partner has exactly the same understanding of the situation that I do. I do this because it's frequently the case that we don't have a lot of overlap in our understanding, or we have very specific gaps or contradictions in our understanding.
If you're like many in this industry, you're working in a language other than what you were raised in, making all of this more difficult.
Average and mean are the same thing. I assume you meant median. It’s similar in this case, but it’s really more like the different between the average of the full list of companies and the average of the full list of companies with the top few hundred removed.
Yes what you are looking for is market-cap weighting (S&P 500) vs "equal weighting" (e.g. the RSP etf) which gives 1 weight to each of 500 stocks, rather than weighting by size of the company.
Not necessarily. Does Waymo really want to run all the additional infra and services and people ops required to be a full soup-to-nuts ride hailing service?
I mean, they do today, but maybe they don't want to be in that business.
... Google did say "No more Oracle EBS" and switched entirely to SAP. It took multiple years, and it was not a small effort, but there was the will, and a way was found.
sigh I didn’t work at FAANG type, we don’t hire FAANG skill level. Whatever Google did is completely irrelevant to this conversation and most other conversations.
In my experience, FAANG are no more skilled than anyone else. The main thing is that they seem to do a better job of not hiring complete duds, so their average cleverness may be higher, but I’ve worked with brilliant people at every regular shop.
I agree but complete duds can really drag your team down as you end up spending a ton of time trying to fix their shortcomings and amount of code written on the Ops side to prevent them from completely screwing everything up is mind boggling.
I've been told that ejections are violent enough that pilots can end up permanently shorter. A short bit of searching turned up this case study of two pilots' injuries/outcomes:
I am reminded when I read "barely developer oriented" that this comes from Google, who run compute and compilers at Ludicrous Scale. It doesn't seem strange that they might optimize (at least in part) for compiler speed and simplicity.
I'm personally in the habit of answering even slightly complex questions by first establishing shared context - that is, I very carefully ensure that my conversational partner has exactly the same understanding of the situation that I do. I do this because it's frequently the case that we don't have a lot of overlap in our understanding, or we have very specific gaps or contradictions in our understanding.
If you're like many in this industry, you're working in a language other than what you were raised in, making all of this more difficult.