ericlewis

no.

much simpler, just pull apart the MT VST :P

I am working on PO-33, doing EMFI.

I still dont understand why people point to this chart as any sort of meaning. Cost per task is a fairly arbitrary X axis and in no way representing any sort of time scale.. I would love to be told how they didn't underprice their model and give it an arbitrary amount of time to work.

US, GA here. My mom was big on tanning and warned of us this (lemons are also bad). I believe she said something about it being used on purpose for tanning, but that you had to be careful or you would badly burn. She probably did that around the late 80s or early 90s.

As a person who works on this kinda stuff I know what they mean. It’s very hard to debug things totally blind.

Higher the precision the better. Use what works within your memory constraints.

If you are using the user attribution with OpenAI (as you should) then they will block that users id and the rest of your app will be fine.

The theory is that you increase the context with more relevant tokens to the problem at hand, as well as its solutions, which in theory makes it more likely to predict the correct solution.

This reminds of a TPU.

I have one of these. It’s not there.

Perhaps it’s because I know human beings that have the exact same operation and failure mode as the LLM here and I’m probably not the only one. Failing at something you’ve never seen and faking through it is a very human endeavor.

My wife is capable of “automatic driving” and I am not. She describes it as a flow state.

You would need both. RAG will have to be part of the process if you want to generate or work on an existing project. Since it stands for Retrieval Augmented Generation. A fancy way of saying an LLM can access documents.