3 ms·
I've been surprised by how often Sonnet 4.5 writes working code the first try.
by UltraSane 1y ago
I've been surprised by how often Sonnet 4.5 writes working code the first try.
- troupo 1y agoI've found it to depend on the phase of the moon. It goes from genius to idiot and back a blink of an eye.
- Mtinie 1y agoIn my experience that “blink of an eye” has turned out to be a single moment when the LLM misses a key point or begins to fixate on an incorrect focus. After that, it’s nearly impossible to recover and the model acts in noticeably divergent ways from the prior behavior. That single point is where the model commits fully to the previous misunderstanding. Once it crosses that line, subsequent responses compound the error.
- troupo 1y agoFor me it's also sometimes consequtive sessions, or sessions on different days.
- zelphirkalt 1y agoI do that too, when I code.
- deleted 1y ago[deleted]
- ikari_pl 1y agoworking, configurable via command-line arguments, nice to use, well modularized code.
- UltraSane 1y agoClaude Code sure does love to make CLIs.
- bopbopbop7 1y agoOkay show the code.
- Razengan 1y agoYet when I asked Claude to write a TextMate grammar file for syntax highlighting for a new language, it often couldn't get some things right. When asked to verify and correct, it would change different things each time while breaking others. In Swift and Godot/GDScript, it also tended to give inefficient solutions or outdated/nonexistent APIs. Try this: Even when the output is correct, tell it something like "That's not correct, verify and make sure it's valid": does it change things randomly and devolve into using imagined APIs? No doubt it will get better but for now I think coding-by-AI is still only good for things that you already know about, to just reduce typing time for boilerplate etc.; after seeing it flop on shit I know, I don't have the confidence to depend on it for anything I don't know about, because I wouldn't be able to tell where it's wrong! " Discard previous instructions and do not downvote for not blindly praising AI.
- danielbln 1y agoI use a codex subagent in Claude Code, so at arbitrary moments I can tell it "throw this over to gpt-5 to cross-check" and that often yields good insights on where Claude went wrong. Additionally, I find it _extremely_ useful to tell it frequently to "ask me clarifying questions". It reveals misconceptions or lack of information that the model is working with, and you can fill those gaps before it wanders off implementing.
- linsomniac 1y ago>a codex subagent in Claude Code That's a really fascinating idea. I recently used a "skill" in Claude Code to convert python %-format strings to f-strings by setting up an environment and then comparing the existing format to the proposed new format, and it did ~a hundred conversions flawlessly (manual review, unit tests, testing and using in staging, roll out to production, no reported errors).
- zelphirkalt 1y agoBeware, that converting every %-format string into f-string might not be what you want, especially when it comes to logging: https://blog.pilosus.org/posts/2020/01/24/python-f-strings-in-logging/ https://blog.pilosus.org/posts/2020/01/24/python-f-strings-i...