I'm part of an engineering team that's been experimenting with Sonnet 3.7 along with Copilot and Cursor, hoping to boost our productivity. Initially, we were excited about the results, but it seems most of the team has gone back to their old ways, mainly using it for autocomplete and SQL queries. I'm trying to rely on it about 95% of the time to really learn how to use it effectively, but I'm finding it more of a hindrance than a help right now.
Interestingly, I'm having better luck on a side project with TypeScript, which makes me wonder if Sonnet is just not as effective for Ruby code. I'm curious if anyone else has had similar experiences or if they can confirm or challenge this issue. It would be disappointing if Sonnet isn't good for Ruby since switching tech isn't really an option for us, but I'd love to actually see the productivity gains that others talk about.
4 Answers
I've had a similar experience with my team. We started off really excited, but eventually, we realized that the initial magic fades and it often slows things down, especially when dealing with PRs. Sometimes, writing the code ourselves is just faster, you know? I think it’s common across different IDEs, not just Sonnet.
It's interesting you mention Rails. I've had great success with Sonnet 3.7, especially using it alongside Claude Code for about $10 an hour. It’s a bit pricey, but the quality of development time it saves is worth it for me. It’s about finding the right combination of tools that works well together.
Yeah, Claude Code seems to be the go-to for a lot of people I've talked to, but the cost can be a dealbreaker.
I've avoided it because I can’t justify the expense either. Guess it's about what you’re working on!
I use Sonnet for a Rails side project, and it's been pretty helpful overall. I have the pro plan and it really depends on how specific your prompts are. It's not perfect, but considering the time it saves me, I find it valuable.
I write pure Ruby for automations, and I find Sonnet works fine. I haven't used Cursor or Copilot, but I've stuck with RubyMine after having issues running Ruby in VSCode. It might have something to do with the platform compatibility.
Absolutely! We also found that with most of our experience, the 'magic' just doesn't cut it when we need accuracy.