pull down to refresh

100 sats \ 3 replies \ @k00b 5 Oct \ on: Opti's Claude 4.5 Sonnet "vibe coding" report AI
I've been using 4.5 in MAX mode in cursor since it was released. It does seem better in some qualitative way. I haven't done a hard vibe with it yet but I was using it to make large changes to my migration and it did a pretty good job.
My biggest gripe is that it more often than not starts on a plausible but faulty premise. It's like it begins recursively reasoning a little too early. Once you've steered it the right way it's pretty great.
After I get my monthly admin done, I'm hoping to vibe some tests with it.
write
preview
50 sats \ 2 replies \ @optimism OP 5 Oct
Hmm. Why did you decide that you needed max mode?
reply
100 sats \ 1 reply \ @k00b 5 Oct
I hadn't used it yet so I was curious. Extra cost is worth it if it produces better results with less effort and purportedly that's what it does. Jury is still out though
reply
100 sats \ 0 replies \ @optimism OP 5 Oct
yeah I'm skeptical about it. I have better results with a clean instruction file and context reset per "task", but I have the issue system now for context, which helps a lot...
even if I just tell Claude to file an issue, then to plan a resolution of that issue, and then to execute the resolution. And clean context between these runs actually works best - I probably will lose some cached tokens this way, but I doubt that it's cheaper to just let it grow forever.
reply