Live data from Hacker News

Lessons after a Half-billion GPT Tokens

kenkantzer.com

11–20 of 179 posts

Re: Lessons after a Half-billion GPT Tokens

#11
The team I work on processes 5B+ tokens a month (and growing) and I'm the EM overseeing that.

Here are my take aways

1. There are way too many premature abstractions. Langchain, as one of may examples, might be useful in the future but at the end of the day prompts are just a API call and it's easier to write standard code that treats LLM calls as a flaky API call rather than as a special thing.

2. Hallucinations are definitely a big problem. Summarizing is pretty rock solid in my testing, but reasoning is really hard. Action models, where you ask the llm to take in a user input and try to get the llm to decide what to do next, is just really hard, specifically it's hard to get the llm to understand the context and get it to say when it's not sure.

That said, it's still a gamechanger that I can do it at all.

3. I am a bit more hyped than the author that this is a game changer, but like them, I don't think it's going to be the end of the world. There are some jobs that are going to be heavily impacted and I think we are going to have a rough few years of bots astroturfing platforms. But all in all I think it's more of a force multiplier rather than a breakthrough like the internet.

IMHO it's similar to what happened to DevOps in the 2000s, you just don't need a big special team to help you deploy anymore, you hire a few specialists and mostly buy off the shelf solutions. Similarly, certain ML tasks are now easy to implement even for dumb dumb web devs like me.

Re: Lessons after a Half-billion GPT Tokens

#12
I agree with most of it, but definitely not the part about Claude3 being “meh.” Claude3 Opus is an amazing model and is extremely good at coding in Python. The ability to handle massive context has made it mostly replace GPT4 for me day to day.

Sounds like everyone eventually concludes that Langchain is bloated and useless and creates way more problems than it solves. I don’t get the hype.

Re: Lessons after a Half-billion GPT Tokens

#13

The team I work on processes 5B+ tokens a month (and growing) and I'm the EM overseeing that. Here are my take aways 1. There are way too many premature abstractions. Langchain, as one of may examples, might be useful in the future but at the end of the day prompts are just a API call and it's easier to write standard code that treats LLM calls as a flaky API call rather than as a special thing. 2. Hallucinations are…

> IMHO it's similar to what happened to DevOps in the 2000s, you just don't need a big special team to help you deploy anymore, you hire a few specialists and mostly buy off the shelf solutions.

I advocate for these metaphors to help people better understand a reasonable expectation for LLMs in modern development workflows. Mostly because they show it as a trade-off versus a silver bullet. There were trade-offs to the evolution of devops, consider for example the loss of key skillsets like database administration as a direct result of "just use AWS RDS" and the explosion in cloud billing costs (especially the OpEx of startups who weren't even dealing with that much data or regional complexity!) - and how it indirectly led to Gitlabs big outage and many like it.

Re: Lessons after a Half-billion GPT Tokens

#14
I share a lot of this experience. My fix for "Lesson 4: GPT is really bad at producing the null hypothesis"

is to have it return very specific text that I string-match on and treat as null.

Like: "if there is no warm up for this workout, use the following text in the description: NOPE"

then in code I just do a "if warm up contains NOPE, treat it as null"

Re: Lessons after a Half-billion GPT Tokens

#15

I agree with most of it, but definitely not the part about Claude3 being “meh.” Claude3 Opus is an amazing model and is extremely good at coding in Python. The ability to handle massive context has made it mostly replace GPT4 for me day to day. Sounds like everyone eventually concludes that Langchain is bloated and useless and creates way more problems than it solves. I don’t get the hype.

Claude is indeed an amazing model, the fact that Sonnet and Haiku are so good is a game changer - GPT4 is too expensive and GPT3.5 is very mediocre. Getting 95% of GPT4 performance for GPT3.5 prices feels like cheating.

Re: Lessons after a Half-billion GPT Tokens

#17
The biggest realisation for me while making ChatBotKit has been that UX > Model alone. For me, the current state of AI is not about questions and answers. This is dumb. The presentation matters. This is why we are now investing in generative UI.

Re: Lessons after a Half-billion GPT Tokens

#18
post #14

I share a lot of this experience. My fix for "Lesson 4: GPT is really bad at producing the null hypothesis" is to have it return very specific text that I string-match on and treat as null. Like: "if there is no warm up for this workout, use the following text in the description: NOPE" then in code I just do a "if warm up contains NOPE, treat it as null"

For cases of “select an option from this set” I have it return an index of the correct option, or eg 999 if it can’t find one. This helped a lot.

Re: Lessons after a Half-billion GPT Tokens

#19
post #14

I share a lot of this experience. My fix for "Lesson 4: GPT is really bad at producing the null hypothesis" is to have it return very specific text that I string-match on and treat as null. Like: "if there is no warm up for this workout, use the following text in the description: NOPE" then in code I just do a "if warm up contains NOPE, treat it as null"

For cases of “select an option from this set” I have it return an index of the correct option, or eg 999 if it can’t find one. This helped a lot.

Smart

Re: Lessons after a Half-billion GPT Tokens

#20
post #14

I share a lot of this experience. My fix for "Lesson 4: GPT is really bad at producing the null hypothesis" is to have it return very specific text that I string-match on and treat as null. Like: "if there is no warm up for this workout, use the following text in the description: NOPE" then in code I just do a "if warm up contains NOPE, treat it as null"

We do this for the null hypothesis - is uses an LLM to bootstrap a binary classifier - which handles null easily

https://github.com/lamini-ai/llm-classifier

Post reply on HN