zlacker

>>Anon84+(OP)
I feel like I must be missing something, but I just cannot understand the hype around Claude Code. Don't get me wrong, I'm fully bought in on using AI for development and am super happy to use Copilot or Cursor, but as an experienced developer just chatting with the terminal feels so wrong. I've tried it so many times to switch and I can't get into it.

Can anyone else share what their workflow with CC looks like? Even if I never end up switching I'd like to at least feel like I gave it a good shot and made a choice based on that, but right now I just feel like I'm doing something wrong.

>>superf+F21
One thing I really like it for is if you have a lot of something similar - let's say plugins. I can then just go to the plugins directory, and tell claude something as simple as "this is the plugins directory where plugins live. I want to add one called 'sample' that samples records". Note that I don't even have to tell it what that means usually.

It will read the existing plugins, understand the code style/structure/how they integrate, then create a plugin called "sample" AND code that is usually what you wanted without telling it specifically, and write 10 tests for it.

In those cases it's magic. In large codebases, asking it to add something into existing code or modify a behavior I've found it to be...less useful at.