RAG, as far as I understand, is a term that came about before LLM tool-calling was as prevalent. Your options were to have an LLM hallucinate up a response, or instead do a [document -> chunk -> embedding -> vector db -> query -> context window] pipeline. I haven't heard anyone talk of LLMs + web search or other tool calls as RAG, even though if you pull apart the semantics the term is applicable. In fact I don't hear people talk about RAG much at all. I suppose much of what people were trying to solve with document chunking/embedding pipelines has been solved with bigger models and tool calls. And along with that change in tooling we have left behind the term "RAG", which leaves it attached to the concept of those pipelines.
Just don't use a Twitter post as your demo video in the GitHub readme. I don't care what someone does on Twitter - I never go there. But you can just embed a .gif or .webm in your readme or link to YouTube there.
It’s tough to write good questions for LLM evaluations. They’re so good at picking up subtleties they can pass a multiple choice test when given only the answers and not the questions.
People optimizing for grades is so sad. I got a BS in CS and no one has ever asked about my grades. I tried to optimize for learning and it turns out that pays off really well once you hit the real world.
Assume you have a fan sitting still. You smack it and it’s now rotating with 1m/s angular velocity. If you want it to go faster you can’t smack it at the same speed. You have to hit it faster else you’re just tickling it and it stays the same speed. So you smack your hand twice as hard and now it’s going even faster. Then three times as hard, four times, etc.
If you sum the smack energy it will be 1+2+3+4, which starts to build out a right isosceles triangle if you graph it. Such a triangle is half of a square, ie: 1/2*v^2.
I can’t imagine software engineers caring about this at all. The only people that care about UI theft are C suite IP clutchers. SWEs generally love being able to use each other’s work. Copying UI by eye has been SOP since the dawn of computing.
I don't know Brian or anyone at Oxide, but for the record nearly every place I have ever passed an interview (and later enjoyed employment at) has had people complain about the process online. Partly I think that's down to nearly everyone having an imperfect interview process. It's hard to do right and you won't fail as a company because you passed on a good candidate. You optimize for rejecting the people that will cause disaster, because those are the people that could cause you to fail. Some of the saltiness I see online must be sour grapes.
It’s a complete embarrassment. They added it for aesthetic alignment with the iPhone 13. And then the 14 removed the notch soon after. They’ve kept it for years since then. It has no functional purpose. It’s not there for face ID or because they couldn’t figure out how to do a hole punch camera.