Earlier quoted context omitted.
The phrase "so damn good" implies a benchmark, which itself is implied to be the average of comparable tools. Without these premises, one could state that the 1996 Yugo was so damn good. I mean, it was better than a horse.
I dunno, horses are pretty great.
What makes Claude Code so damn good
281–290 of 322 posts
Re: What makes Claude Code so damn good
#282Earlier quoted context omitted.
Do you ever fix your own bugs?
Bugs, yes. Security vulnerabilities? Rarely enough that it wouldn’t make my HN list. It’s not remotely hard to avoid the most common issues.
It wasn't something I considered at first but it makes sense if you think about text prediction models and infilling and training by reading code. The statistics of style matching what you are doing against similar things. You're not going to paint a photorealistic chunk into a hole of an impressionist painting, ya know?
So in my experience if you give it "code that avoids the common issues" that works like a style it will follow. But if you're working with a codebase that looks like it doesn't "avoid those common issues" I would expect it to follow suit and suggest code that you would expect from codebases that don't "avoid those common issues". If the input code looks like crappy code, I would expect it to statistically predict output code that looks like crappy code. And I'm not talking about formatting (formatting is for formatters), it's things like which functions and steps are used to accomplish whatever. That sort of thing. At least without some sort of specific prompting it's not going to jump streams.
Edit: one amusing thing you can do is ask Claude to predict attributes of the developers of the code and their priorities and development philosophy (i.e. ask Claude to write a README that includes these cultural things). I have a theory it gives you an idea about the overall codesmell Claude is assigning to the project.
Again I am very new to these tools and have only used claude-code because the command line interface and workflow didn't make me immediately run for the hills the way other things have. So no idea how other systems work, etc because I immediately bounced on them in the past. My use of claude-code started as an "okay fine why not give these things the young guns can't shut up about a shot on the boring shit and maybe clear out some backlog" for making chores in projects that I usually hate doing at least a little interesting but I've expanded my use significantly after gaining experience with it. But I have noticed it behave very differently in different code bases and the above is how I currently interpret that.
Re: What makes Claude Code so damn good
#283Earlier quoted context omitted.
I've used Claude Code, Cursor, and Copilot is Vscode and I don't "know" that Claude Code is better apart from the fact that it runs in the terminal, which makes it a little faster but less ergonomic than tools running inside the editor. All of the context tricks can be done with Copilot instructions as well, so I simply can't see how Claude Code is superior.
I’ve been so into Claude code that I haven’t used cursor or copilot in vs code in a while. Do they also allow you to view the thinking process and planning, and hit ESC to correct if it’s going down a wrong path? I’ve found that to be one of my favorite features of Claude code. If it says “ah, the the implementation isn’t complete, I’ll update test to use mocks” I can interrupt it and say no, it’s fine for the test t…
Re: What makes Claude Code so damn good
#284Earlier quoted context omitted.
I've used Claude Code, Cursor, and Copilot is Vscode and I don't "know" that Claude Code is better apart from the fact that it runs in the terminal, which makes it a little faster but less ergonomic than tools running inside the editor. All of the context tricks can be done with Copilot instructions as well, so I simply can't see how Claude Code is superior.
I’ve been so into Claude code that I haven’t used cursor or copilot in vs code in a while. Do they also allow you to view the thinking process and planning, and hit ESC to correct if it’s going down a wrong path? I’ve found that to be one of my favorite features of Claude code. If it says “ah, the the implementation isn’t complete, I’ll update test to use mocks” I can interrupt it and say no, it’s fine for the test t…
Re: What makes Claude Code so damn good
#285So, what great new products or startups have these amazing coding agents helped create so far (and not on the AI supply side). Anywhere to check?
literally every single startup in the past year is helped by these. Of course you haven't heard of them, they're year-old startups
Re: What makes Claude Code so damn good
#286I've literally built the entire MVP of my startup on Claude Code and now have paying customers. I've got an existential worry that I'm going to have a SEV incident that will trigger a house of falling cards, but until then I'm constantly leveraging Claude for fixing security vulnerabilities, implementing test-driven-development, and planning out the software architecture in accordance with my long-term product roadma…
> I've literally built the entire MVP of my startup on Claude Code and now have paying customers. Would you mind linking to your startup? I’m genuinely curious to see it. (I won’t reply back with opinions about it. I just want to know what people are actually building with these tools!)
Re: What makes Claude Code so damn good
#287Earlier quoted context omitted.
[flagged]
I generally work as openly as possible on github, and I am deliberately avoiding manual coding for a while to try to learn these (infuriating/wonderful) tools more thoroughly. Unfortunately I can't always share all of my work, but everything on github after perhaps 2025-06-01 is as vibe-coded as I can get it to be. (I manually review commits before they're pushed, and PRs once in a complete state, but I always feed t…
Re: What makes Claude Code so damn good
#288Re: What makes Claude Code so damn good
#289I've literally built the entire MVP of my startup on Claude Code and now have paying customers. I've got an existential worry that I'm going to have a SEV incident that will trigger a house of falling cards, but until then I'm constantly leveraging Claude for fixing security vulnerabilities, implementing test-driven-development, and planning out the software architecture in accordance with my long-term product roadma…
> I've literally built the entire MVP of my startup on Claude Code and now have paying customers. Would you mind linking to your startup? I’m genuinely curious to see it. (I won’t reply back with opinions about it. I just want to know what people are actually building with these tools!)
Re: What makes Claude Code so damn good
#290Earlier quoted context omitted.
Answered above, but to be concrete on features --> it helped me build an end-to-end multi-stage pipeline architecture for video and audio transcription, LLM analysis, content generation, and evals. It took care of stuff like Postgres storage and pgvector for RAG-powered semantic search, background job orchestration with intelligent retry logic, Celery workers for background jobs, and MCP connectors.
We get it; it helped you build a bunch of stuff. Why not just post your company?