4 ms·
I'm curious in what kinda if situations you are seeing the model the do opposite of your intention consistently where the instructions were not complex. Do you
by alienbaby 10mo ago
I'm curious in what kinda if situations you are seeing the model the do opposite of your intention consistently where the instructions were not complex. Do you have any examples?
- avereveard 10mo agoMostly gemini 3 pro when I ask to investigate a bug and provide fixing options (i do this mostly so i can see when the model loaded the right context for large tasks) gemini immediately starts fixing things and I just cant trust it Codex and claude give a nice report and if I see they're not considering this or that I can tell em.
- saxenaabhi 10mo agofyi that happened to me with codex. but, why is it a big issue? if it does something bad, just reset the worktree and try again with a different model/agent? They are dirt cheap at 20/m and I have 4 subscription(claude, codex, cursor, zed).
- prmph 10mo agoThe issue is that if it's struggling sometimes with basic instruction following, it's likely to be making insidious mistakes in large complex tasks that you might no have the wherewithal or time to review. The thing about good abstractions is that you should be able to trust in a composable way. The simpler or more low-level the building blocks, the more reliable you should expect them to be. In LLMs you can't really make this assumption.
- saxenaabhi 10mo agoI'm not sure you can make that assumption even when a human wrote that code. LLMs are competing with humans not with some abstraction. > The issue is that if it's struggling sometimes with basic instruction following, it's likely to be making insidious mistakes in large complex tasks that you might no have the wherewithal or time to review. Yes, that's why we review all code even when written by humans.
- avereveard 10mo agoSame I have multiple subscription and layer them. I use haiku to plan and send queue of task to codex and gemini whose command line can be scripted The issue to me is that I have no idea of what the code looks like and have to have a reliable first layer model that can summarize current codebase state so I can decide whether the next mutation moves the project forward or reduces technical debt. I can delegate much more that way, while gemini "do first" approach tend to result in many dead ends that I have to unravel.