Long story short, it seems to be faster and less vocal but not much dumber (it's just my thinking partner, so I read a lot of the output as I create a large data model).
I read this as "the code is working as intended but the bug is an artifact of the original design"
I'm a native English speaker as well, I shudder to think what a second language speaker would do (even if they were very confident with the language!).
Good for more precise changes.
I would never have predicted this a year ago.
I always scoffed about engineers not doing work during Github outages - I'd always find some kind of other engineering to do if PRs or builds were piling up.
But during model outages, and since I'm not actively set up to use OpenAI/Codex at the moment, I'll just find something else productive to do. I don't think I'm ever going to write code by hand again unless I'm fixing something the AI can't manage or the change is small enough. Why even try when the machine is 100x faster?
Should I give Codex another try? It's been a month or so since I last used it, and it always felt inferior at Rust and TypeScript.
switching subs is kind of a PITA since you need to commit to a month at least
The verbosity of Opus 5 isn't even my issue, it's consistency. For every 10 tasks Opus 5 accomplishes, there's at least one task that Opus 5 does just an atrocious job of, or a debugging investigation that it just completely goes off the rails on.