Hacker News
points by rbehrends 3 days ago | 0 comments
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?
[–] redox99 3 days ago
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.
[–] rbehrends 3 days ago
You said above that "Opus 5.5 still makes a lot of mistakes". This seems to contradict what you are saying here?
[–] redox99 3 days ago
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.

[–] dca88 3 days ago
I am genuinely curious, at what point did you find yourself comfortable “YOLO merging without looking at the code”?

I struggle to find myself ever feeling comfortable doing this in a production environment at my day job.

[–] redox99 3 days ago
Probably around GPT 5.6 Sol.

These days your average Opus 5.5 PR with multiple passes of review by Opus 5.5 and Sol 6.1 agents is much less likely to contain bugs than your pre-AI PR.

[–] rbehrends 3 days ago
I think this is where we may have to agree to disagree, because this not something that I'd do outside of toy projects. Not necessarily because I'm worried about the correctness of a single MR (in fact, it may very well be more likely to be correct than a human-authored and -reviewed one), but because I'm concerned about the accrual of technical debt. Even if each individual MR is correct, the trajectory for code quality can trend downwards.

The recent update to SlopCodeBench that includes Astra and Opus 5.5 (including the insight that higher reasoning levels may not improve the situation) seems to match my intuition. [1]

[1] https://github.com/humanlayer/advanced-context-engineering-f...

[–] redox99 2 days ago
That benchmark only prompts the agent once. You shouldn't do that. The first implementation of agents is very often flawed.

My pipeline is

Opus implements -> Opus and Sol review changes -> Opus verifies the issues from the reviews are real and worth fixing -> Opus fixes the issues.

[–] agile-gift0262 3 days ago
But sounds like Opus and GPT are interchangeble for your case.
[–] redox99 3 days ago
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.