> I refused to believe that there was no option to change the time (...) I decided to fetch the firmware and dig into it
That must be one of the most iconic HN sentences ever.
That must be one of the most iconic HN sentences ever.
If I ask my Claude (Opus 5.5) about how some Claude feature works, its natural inclination is to start reversing its own binary with strings instead of looking at Anthropic's documentation. It will, entirely unprompted, try to figure out how its environment works in Claude Code cloud and reverse–reverse-engineer Anthropic's Rust binaries to figure out why things happen the way they do, and what it needs to do about it.
However Claude and I did write code all the day long and a long job went down from 2+ hours to 30 minutes, same final output.
Where OpenAI will go out of its way to search the internet and cite sources, Claude will typically just go from memory and common sense. I'm half-tempted to write myself a hook that greps my responses for "haven't verified" and "haven't checked" and asks it to do so.
There are tradeoffs to this ofc; just using weights is more token efficient and faster, and there are situations where the model genuinely knows and doesn't have to check. Anthropic models seem better calibrated with regards to knowing what they do know and what they don't (and openly admitting what they haven't yet checked to the point of pedantry), whereas OpenAI models seem to err on the side of caution and check everything just in case. Of course, if you are so inclined, you could use either behavior to spin a conspiracy-theory-minded narrative about how "Anthropic is deliberately nerfing their models to save on compute" or how "OpenAI is wasting your tokens to get more money out of you without increasing sticker prices."