Comment by rbehrends
20 hours ago
Yeah, but that's also a large part of why they remain interchangeable, I would say. I feel like we may be talking past each other?
20 hours ago
Yeah, but that's also a large part of why they remain interchangeable, I would say. I feel like we may be talking past each other?
They are interchangeable maybe in your case. In my case for my tasks and for my product, Opus and GPT are at a level where I can vibe code with them and trust them, whereas the others aren't really there. When models get better they'll reach whatever point you need to be able to trust them.
You said above that "Opus 5.5 still makes a lot of mistakes". This seems to contradict what you are saying here?
Sorry just woke up, I wasn't being clear.
There's two thresholds.
1. Tasks models can do. 2. Tasks models can do with enough reliability that you can YOLO merge without looking at the code.
Most models can do most of 1. That's no longer the interesting part.
2. is quickly expand. I can trust opus 5.5 enough with easy to medium tasks that I can YOLO merge them. For open models, I can only trust them with easy tasks if I want to YOLO merge.
I'd love to have a stronger model that I can trust to YOLO merge hard tasks.
3 replies →
But sounds like Opus and GPT are interchangeble for your case.
Both have good models. My workflow these days is usually Opus plans and codes, then Opus and Sol review, finally Opus verifies the review and applies fixes.