Comment by sdesol

Comment by sdesol 4 days ago

I don't disagree that we need to be cautious with LLMs, but I've personally stopped asking GPT-4/GPT-4 mini for technical answers. Sonnet 3.5 and DeepSeek V3 (which is much cheaper but still not as good as Sonnet) are your best bet for technical questions.

Where I find GPT to perform better than Sonnet is with text processing. GPT seems to better understand what I want when it comes to processing documents.

I'm convinced that no LLM provider has created or will create a moat, and that we will always need to shop around for an answer.

wegfawefgawefg 4 days ago

everyone stopped using 4/4mini because theyre old.

4o replaced 4 back in April 2024. 01/01mini replaced 4o in Fall 2024.

stop using 4. use 01mini always. its cheaper, faster, and better.

o1/o1mini will be replaced by o3/o3mini in a couple months.

Reply View 4 replies

sdesol 4 days ago

Unfortunately you need to be tier 2 to use o1-mini. The only time I really use GPT is to summarize documents and for that, GPT-4o mini works well enough and it is significantly cheaper than other high quality models, so I never really rack up an OpenAI bill.

Reply View | 0 replies
mistercheph 3 days ago

o1 is such a joke, worse than 4o in some ways like multiturn,
The months old sonnet feels a generation ahead of any OAI product I've used, I'll believe the hype on o3 when I see it, remember the sora and voice roll out?

Reply View | 2 replies
- wegfawefgawefg 3 days ago
  
  You may want to reconsider this position.
  I had this bizarre bug in rust networking code where packets were getting dropped.
  i dumped all 20k lines into o1pro. it thought for about ten minutes and came back telling me that my packets had a chance of being merged if set in quick succession and i needed to send the length before each message and scan packets in a loop for subdivisions on the client. this bug hadnt happened before, only when running locally on a newer faster machine, and was frequent but hard to replicate.
  it was correct, and provided detailed pseudo code to solve it.
  the second case involved some front end code where during an auth flow ios would force refresh on returning to the browser causing authentication state to be lost. o1pro thought for about 5 minutes before telling me ios has a heuristic with which it decides to close an app on context switch based on available ram, etc, and that i needed to conditionally check for ios and store partial state in local store on leave assuming the app could be deloaded without my control.
  it was correct. with some more back and forth we fixed the bug.
  these are not the kinds of problems that claude and gpt<4 have been able to help with at all.
  I also used voice, and video voice extensively for translation tasks in korea, japan, and taiwan, and for controlling japanese interfaces and forms for tax documents and software.
  These are very good tools.
  
  Reply View | 0 replies
- Philpax 3 days ago
  
  o1 is not a general-purpose model, and it's not very good at multi-turn; it should instead be given all the context upfront: https://www.latent.space/p/o1-skill-issue
  
  Reply View | 0 replies