609 karma · joined May 24, 2023
I have no idea where the myth of ‘can’t add new knowledge via fine-tuning’ came from. It’s a sticky meme that makes no sense.
Pretraining obviously adds knowledge to a model. The difference between pretraining and fine-tuning is the number of tokens and learning rate. That’s it.
Her age is relevant when discussing the future of SpaceX, considering the median retirement age.
If your product is a social graph w/ ads (Meta), you can.
It's hardly corporate charity:
* Meta releasing these models creates an improvement and tuning ecosystem around it, giving them access to tons of free developer time.
* It's also a strong recruiting tool, for engineers and researchers frustrated by, e.g., Google and OpenAI becoming increasingly closed. They know they can publish at Meta.
* The cost is insignificant. Meta had 30B in revenue just in Q2 2023.
But that doesn't imply what you're saying unless the supplier has monopoly power, which they, by law, do not.
There's a few obvious exceptions, but plenty of insurance isn't required.
LIMA demonstrated that instruction-tuning and output formatting could be trained with a limited number of samples, not that finetuning was incapable of adding new information to the model.
It may be sub-optimal in most cases to RAG, but it does work.
Postmasters at large ESPs and inbox providers can and will text each other to resolve issues.
This is pretty much how the internet works as well (BGP, etc). It's opaque, but open.
It's closer to a craftmanship kind of care. Being proud of what you're putting into the world. Caring that it works well, not because the purpose is important, but because it's something you're doing and you want to do it well.
Wikipedia has a fun example:
> The Wyoming House of Representatives Committee of the Whole amended House Bill 0085, a proposal to study the state's emergency preparedness, in order to kill the bill. The amendment would have required the state to consider purchasing an aircraft carrier (even though Wyoming is a landlocked state), purchasing fighter jets, establishing a military, initiating a draft, and creating a currency.
There is a popular perception that:
- If Democrats are in the minority and want to block a Republican bill, they will attempt to drum up public pressure, advocate on the floor and with individual legislators, etc.
- If Republicans are in the minority and want to block a Democrat bill, they will by any means necessary. They'll use various edge cases of parliamentary procedure, attach/amend/manipulate bills to poison them, etc. 'Playing dirty'.
I have no idea if this is actually true, but it's a common idea I've heard from both sides. The Democrats see it as a sign of their moral superiority, and the Republicans see it as an demonstration of conviction.
A good sysadmin was always doing the same thing as a good SRE.
Complexity is very, very expensive.
This was the pitch from my manager that led to me moving into an EM role. He knew I was interested in doing a startup in the future, but I didn't have experience with people management.
I don't think it's necessarily a great path to entrepreneurship, but if you are solid on the engineering side it's a good skillset to develop.
There are plenty of levers to pull that are not salary, and not based on geography.
This is the difference. I don't see it as arbitrarily paying more than I need to. I see it as paying people the same for doing the same work. My goal is not to pay as little as possible, or even to pay a high rate relative to their local market.
I can't look at someone in Romania doing the same job as someone in Chicago and tell them I'm paying them less because they're in Romania.
I completely understand that this is not economically optimal, and I love capitalism. I just have no interest in saving money this way.
> So you could try to set a median pay that's higher than the LCOL targets but lower than Bay Area salaries. Now you're attractive to some talent, but other people won't consider your company because it pays less than their alternatives.
Salary is only one part of comp. Comp is only one part of what makes a company attractive.
The problem is that there are now multiple generations of software engineers that do not know how bandwidth is priced. They've only used managed providers that charge per unit of ingress/egress, at some fractional dollar per GB.
Whereas in CUDA programming, a kernel is just the code running on the device. When I first heard kernel in relation to CUDA programming, I expected it to be a) the actual OS kernel, and then b) something akin to a GPU driver.
I can see how NVIDIA got there, but it's not immediately obvious if you're coming from a SWE context.
There are a few people genuinely concerned, however misguidedly, about the outputs of LLMs. The big money coming into the field from EAs and the sort of background fear is about fast takeoff, shoggoths, paperclip maximizers, etc.
The thought is that, if you can't reliably align an LLM to output what some authoritative source wants, then you can't reliably align the inevitable machine god that will destroy us.
In that context, user education doesn't do any good.