
What I like most about Claude is that I can actually give it a large amount of context and work through a problem instantly. As a computer science student, I use Claude quite regularly for my Placement interview as well as DSA practice, coding, project development. The ui is also feels minimal.
A lot of my DSA and interview practice involves getting stuck on a problem and trying to understand why my approach isn't working. I use Claude to discuss the approach, check my reasoning and then go back and implement it myself. I also use it when working on projects with my team where there are multiple files and I need to understand how one part of the code affects another and the overall repo.
Recently, I also used Claude while working on a project for a Razorpay buildathon with my team. It was useful for going through parts of the project, discussing implementation decisions and helping me think through changes instead of just asking it to generate code. That longer context is probably the feature I use the most. Review collected by and hosted on G2.com.
The main thing that annoys me is the usage limit. When I'm working through a complicated coding problem or project, I can go through a lot of messages fairly quickly and then have to wait before I can continue. I also don't blindly use the code it gives me. Sometimes a solution looks correct at first but doesn't quite fit the way my project is structured, so I still have to test it and make changes myself. Other than that, everything else looks fine. Review collected by and hosted on G2.com.