Comment by Keats

5 days ago

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?

16 comments

Keats

Reply
dimitri-vs  5 days ago

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  5 days ago

    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  5 days ago

    > 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  5 days ago

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  5 days ago

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

    • Keats  5 days ago

      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.

      2 replies →

    • exfalso  5 days ago

      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  5 days ago

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

bananapub  5 days ago

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.