Live data from Hacker News

My experience with Claude Code after two weeks of adventures

sankalp.bearblog.dev

281–290 of 388 posts

Re: My experience with Claude Code after two weeks of adventures

#281
post #243

Earlier quoted context omitted.

I used to feel similarly. But recently started using Claude Code and it does feel a lot better than Cursor for me I'm not sure why. However, Claude does seem to know better where things are and knows not to make unnecessary changes. I still need to guide it and tell it to do things differently some times, but it feels like it's a lot more effective Personally, I also like that usually it just presents to me only one…

> Personally, I also like that usually it just presents to me only one change/file at a time, so it's easier for me to review This is interesting. I haven't used Cursor, but one of my frustrations with Claude Code is that some of the individual changes it asks me to approve are too small for me to make a decision. There are cases where I almost denied a change initially, then realized Claude's approach made sense onc…

> some of the individual changes it asks me to approve are too small for me to make a decision. There are cases where I almost denied a change initially, then realized Claude's approach made sense once I saw the full change set

Yes, I've adapted to just review quickly, then if it makes sense as part of the task, let it keep going until it's done with the whole thing. Most of the times, by the end it does the right thing

I love that it doesn't auto-commit everything, ala aider, so it's pretty painless to undo stuff

I also keep a TODO.md file with a plan of everything I want to do for the current ticket/PR. I tell CC to keep track of things there. CC takes stuff from there, breaks it down into its own subset of tasks and when finished I tell it to update the TODO.md with the progress. I also tell it to stage files and create commits

The way I use it, it feels like I'm still programming, but I don't need to write code or run commands by myself, nor get stuck googling stuff up. I can just tell CC to do almost anything for me. It takes away the tediousness of what I want to accomplish

Re: My experience with Claude Code after two weeks of adventures

#282
I've been getting a lot of alpha out of Claude Code, but struggling a bit with how to bring it to the rest of my team. Does anyone have any practical advice on sharing best practices or generally getting team members or folks you supervise to also benefit from Claude Code?

Re: My experience with Claude Code after two weeks of adventures

#283
post #107

Earlier quoted context omitted.

that's really just a scale question. Yes, I would write a 4 line bash script by myself. But if you're trading a 200 line comprehensive claude.md document for a module that might be 20k LoC? it's a different value proposition.

And how do you actually know that those 20k line of codes have no glaring bugs, or bugs that you can find yourself, or be able to understand it completely at some point?

How do you know your own handwritten 20k lines of code have no bugs, or that 20k lines of code written by coworkers have no bugs?

Re: My experience with Claude Code after two weeks of adventures

#284

Reading all these glowing reviews of Claude Code, I still get the feeling that either everyone’s been paid off or it’s just the die-hard fans of terminal windows and editors like Emacs and Vim. Using the terminal is right up their alley—it’s in their DNA. Every time I read comments saying Claude Code is far better than Cursor, I fire it up, pay for a subscription, and run it on a large, complex TypeScript codebase. F…

My biggest piece of starting advice would be use it for exploration not generation. It can be great for understanding code bases and looking at git history.

Context is key, so it is also really helpful having a CLAUDE.md file; the /init command can create one for you.

If you are going to use it for generation (writing code); plan mode is a must. Hit shift-tab twice.

Finally; I'm mostly using the claude 4 sonnet model, but make sure to tell it to "ultrathink" (use those words); this means it can use more thinking tokens.

Re: My experience with Claude Code after two weeks of adventures

#285

Earlier quoted context omitted.

Some of it is taste. Personally, I dislike VSCode and its descendants; it feels bloated and like I’m always being advertised to inside the product. I want my editor to disappear from thought, and Sublime does this for me. In that context, CC is amazing.

That's funny I always considered Sublime to be more in my face, begging for money every time I opened it.

There's a neat trick to remove the nag screen

Re: My experience with Claude Code after two weeks of adventures

#286

Earlier quoted context omitted.

Some of it is taste. Personally, I dislike VSCode and its descendants; it feels bloated and like I’m always being advertised to inside the product. I want my editor to disappear from thought, and Sublime does this for me. In that context, CC is amazing.

That's funny I always considered Sublime to be more in my face, begging for money every time I opened it.

[deleted]

Re: My experience with Claude Code after two weeks of adventures

#287
post #285

Earlier quoted context omitted.

That's funny I always considered Sublime to be more in my face, begging for money every time I opened it.

There's a neat trick to remove the nag screen

That’s one purchase I never regretted. Sublime was so perfect before writing code got tipped upside down

Re: My experience with Claude Code after two weeks of adventures

#288

Reading all these glowing reviews of Claude Code, I still get the feeling that either everyone’s been paid off or it’s just the die-hard fans of terminal windows and editors like Emacs and Vim. Using the terminal is right up their alley—it’s in their DNA. Every time I read comments saying Claude Code is far better than Cursor, I fire it up, pay for a subscription, and run it on a large, complex TypeScript codebase. F…

Cursor and code completion is such a time saver for me. Having the next few lines guessed feels magic.

Having an agent completely design/write a feature still feels weird. I like everything being hand written, even if I actually just tab completed and edited it slightly

Re: My experience with Claude Code after two weeks of adventures

#289

Earlier quoted context omitted.

I find amazing all the effort that people put trying to program a non deterministic black box. True courage.

Our brains are non deterministic black box. We just don't like to admit it.

"This system has severe limitations. But we should rely more on it because this other system is also limited."

For several decades we've developed and use computers because they can be very precise and deterministic.

Re: My experience with Claude Code after two weeks of adventures

#290

Reading all these glowing reviews of Claude Code, I still get the feeling that either everyone’s been paid off or it’s just the die-hard fans of terminal windows and editors like Emacs and Vim. Using the terminal is right up their alley—it’s in their DNA. Every time I read comments saying Claude Code is far better than Cursor, I fire it up, pay for a subscription, and run it on a large, complex TypeScript codebase. F…

I used it for 2 weeks with the cheap $17/mo sub. It is equal parts amazing, and frustrating.

I ended up with 8k lines of rust and 12k lines of markdown. I think those markdown designs and explicit tasks were required the same way unit tests with a test harness are required to make the human-tool interaction work.

However, I’m not sure if the ‘magic’ is VC-subsidy or something else.

It did make rust (a language i do not know) feel like a scripting language. … the github repo is ‘knowseams’.

Post reply on HN