G2

Thabrash S.

QA Engineer

Small-Business (50 or fewer emp.)

11/1/2026

"Usable, Reasoned Coding Help That Handles Messy Debugging Inputs"

4.5/5

What do you like best about Claude?

I’m a software engineer and I use Claude mostly for coding. Debugging, writing tests, refactoring, and making sense of code I didn’t write. What I like best is that the answers are actually usable. I paste in an error or a chunk of code, and it tells me what’s wrong and why, so I can check the reasoning myself before I commit anything.

It’s also good with messy input. I don’t have to clean up stack traces or write a long explanation first, I just dump it in and it picks out the relevant part. And when it gets something wrong and I point it out, it fixes the problem instead of saying “you’re right” and giving me the same code again.

I also use it for docs, PR descriptions and emails, and the writing needs very little editing. Review collected by and hosted on G2.com.

What do you dislike about Claude?

Sometimes it gives an answer that sounds confident but is wrong, especially with newer libraries or recent version changes. I’ve had it suggest functions or options that don’t exist, so I always have to run and test the code instead of trusting it blindly.

On bigger tasks it can also lose track of earlier details in a long conversation, and I end up pasting the same context again. Some answers are also longer than they need to be, and I have to ask it to keep it short.

Usage limits are another annoyance. When I’m deep in a debugging session, hitting the limit breaks my flow. Review collected by and hosted on G2.com.

What problems is Claude solving and how is that benefiting you?

The main problem it solves for me is the time I lose on small, annoying tasks that add up over a week. Reading through a stack trace, figuring out why a test is failing, writing boilerplate, or trying to understand a piece of code someone else wrote. Instead of searching through docs and forum threads for an hour, I can paste the problem in and get a starting point in a minute or two.

It also helps with the writing side of the job that I don’t enjoy much, like PR descriptions, documentation and emails. That used to eat a chunk of my time and now it’s mostly a quick edit.

The benefit for me is mainly speed and less context switching. I spend more time on the actual design and decisions, and less time stuck on things that are tedious but not hard. It also helps when I’m working with a language or tool I don’t know well, because I can ask it to explain things as I go instead of stopping to read a whole tutorial. Review collected by and hosted on G2.com.