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
Workflow is this: - I have emacs open for code editing/reviews/git. - Separate terminal emulator with 1-3 claudes - I work on a story by splitting it into small steps ("Let's move this email logic to the email.service.ts", "here's the fields I'd need to add to the request, create a schema validation in a separate file, and update the router and controller") - I mostly watch claude, and occasionally walk through the code in emacs whenever I feel like I want to review code. - I handle external tools like git or db migrations myself not letting LLMs near them.

In essence, this is pretty much how you'd run a group of juniors - you'd sit on slack and jira diving up work and doing code reviews.

>>thefly+J41
At that point though isn't it just as fast/easy to cut/paste the code yourself? That was my conclusion after spending a week breaking things down - I was able to get good code out of the AI, but only after spending as much time writing the prompt as if I just did it myself. (note that this was my first attempt at using an agent, maybe I'll learn to do it better)