[Keats]

I've been trying Claude Code with Sonnet 4.0 for a week or so now for Rust code but it feels really underwhelming (and expensive since it's via Bedrock right now). Everytime it's doing something it's missing half despite spending a lot of time planning at the beginning of the session. What am I missing?

[dimitri-vs]

Same. I have a very efficient workflow with Cursor Edit/Agent mode where it pretty much one-shots every change or feature I ask it to make. Working inside a CLI is painful, are people just letting Claude Code churn for 10-15 minutes and then reviewing the diff? Are people even reviewing the code?

[danielbln]

This sort of asynchronous flow will become more and more mainstream. chatgpt.com/codex, Google's Jules and to a degree Claude Code (even though that's local) are all following that pattern: phrase a goal, send it off to the agent, review the diff and request changes, rinse and repeat until ready for PR review.

For me this only works for fairly tightly scoped tasks that aren't super complex, but it does work. And I think the days of staring down the IDE will be coming to a close for all but the most complex coding tasks in the future.

[apwell23]

> Are people even reviewing the code?

No because its boring. Thats why we don't have airplane pilots just watch the machine thats fully on autopilot.

[exfalso]

Exact same experience. I have no clue what other people are doing. I was hunting for use cases where it could be used and it kept not working. I don't get it.

[energy123]

Is it only Rust that you've had this experience with or is it a general thing?

[Keats]

I'm not sure if it's Rust related. It manages to write the Rust code just fine, it's just that it doesn't seem to

- think of everything that is needed for a feature (fixable via planning at the beginning)

- actually follow that plan correctly

I just tried with a slightly big refactor to see if some changes would improve performance. I had it write the full plan and baseline benchmarks to disk, then let it go in yolo mode. When it was done it only implemented something like half of the planning phases and was saying the results look good despite all the benchmarks having regressed.

[furyofantares]

I get a ton of value out of Claude Code but you just listed a lot of things I've found LLMs/agents not very good at.

- Rust

- Big refactors

- Performance improvements

- Yolo-mode, especially if you aren't skilled yet at prompting and knowing which things the LLM will do well and which will need supervision

[bitwize]

I've encountered human Rust programmers that exhibit this behavior. I think that Rust may be falling victim to its own propaganda, as developers come to believe that the borrow checker will fix their logic errors, not just flag up memory management that's at risk of buffer overflow or UAF.

[exfalso]

Also tried it with Python. The autocomplete there was ok-ish(although to me the "wait for it -> review suggested code" cycle is a bit too slow), but getting it to code even standalone well-defined functions was a clear failure. I spent more time trying to fix prompts than it took to write the functions in the first place.

[andyferris]

I had been trying with Rust, but after this article I think I might change tack and attempt a project in Go...

[bananapub]

it shouldn't be expensive - you can pay for Pro ($20/month) or Max ($100 or $200/month) to get what would cost >> $1000/month in API costs.

[andyferris]

Can you use Claude Code with Pro? I was trying to figure this out and I thought you couldn't (unless you enter an API key and pay for tokens).

[bananapub]

https://news.ycombinator.com/item?id=44179604

[andyferris]

Thanks

[rolisz]

Yes, since last week or so.

[Keats]

Yep i know but I have free AWS credits sooo