←back to thread

2127 points bakugo | 8 comments | | HN request time: 0.336s | source | bottom
Show context
anotherpaulg ◴[] No.43164684[source]
Claude 3.7 Sonnet scored 60.4% on the aider polyglot leaderboard [0], WITHOUT USING THINKING.

Tied for 3rd place with o3-mini-high. Sonnet 3.7 has the highest non-thinking score, taking that title from Sonnet 3.5.

Aider 0.75.0 is out with support for 3.7 Sonnet [1].

Thinking support and thinking benchmark results coming soon.

[0] https://aider.chat/docs/leaderboards/

[1] https://aider.chat/HISTORY.html#aider-v0750

replies(18): >>43164827 #>>43165382 #>>43165504 #>>43165555 #>>43165786 #>>43166186 #>>43166253 #>>43166387 #>>43166478 #>>43166688 #>>43166754 #>>43166976 #>>43167970 #>>43170020 #>>43172076 #>>43173004 #>>43173088 #>>43176914 #
bearjaws ◴[] No.43164827[source]
Thanks for all the work on aider, my favorite AI tool.
replies(1): >>43166454 #
bt1a ◴[] No.43166454[source]
It really is best in slot. Owe it to git, which has a particular synergy with a hallucination-prone but correctable system
replies(1): >>43167992 #
1. doctoboggan ◴[] No.43167992[source]
I like Aider but I've turned off auto-commit. I just can't seem to let the AI actually commit code for me. Do you regularly let Aider commit for you? How much do you review the code written by it?
replies(4): >>43168124 #>>43168129 #>>43168132 #>>43168166 #
2. bitbuilder ◴[] No.43168124[source]
The auto-commits of Aider scared the crap out of me at first too, but after realizing I can just create a throwaway branch and let it run wild it ended up being a nice way to work.

I've been trying to use Sonnet 3.7 tonight through the Copilot agent and it gets frustrating to see the API 500 halfway through the task list leaving the project in a half baked state, and then and not feeling like I have a good "auto save" to pick up again from.

3. sejje ◴[] No.43168129[source]
I don't let it auto commit, either. I don't like committing in a broken state, and the llm breaks things plenty often.
replies(2): >>43168270 #>>43168969 #
4. itgoon ◴[] No.43168132[source]
I create a feature branch, do the work and let it commit. I check the code as I go. If I don't like it, then I revert to a previous commit. Other times I write some code that it isn't getting right for whatever reason.

When it's ready, I squash merge into main.

5. joshstrange ◴[] No.43168166[source]
I originally was against auto commit as well, but now I can’t imagine not using it. It’s essentially save points along the way. More than once, I’ve done two or three exchanges with Aider only to realize that the path that we were going down was not a good one.

Being able to get reset back to the last known good state is awesome. If you turn off auto commit, it’s a lot harder to undo one of the steps that the model takes. It’s only a matter of time until it creates nonsense, so you’ll really want the ability to roll it back.

Just work in a branch and you can merge all commits if you want at the end.

6. MyOutfitIsVague ◴[] No.43168270[source]
What's wrong with committing in a broken state if you squash those into a working state before pushing?
replies(1): >>43171409 #
7. fragmede ◴[] No.43168969[source]
The beauty of git is that local commits don't get seen by anybody until you push. so you can commit early and commit often, since no one else is gonna see it, which gets you checkpoints before, during, and after you dive into making a big breaking change in the code. once you've got something you like, then you can edit, squash, and reorder the local commits and clean them up for consumption by the general public.

But to each their own!

8. sejje ◴[] No.43171409{3}[source]
Maybe nothing, I just don't work that way.