Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How I use every Claude Code feature

blog.sshh.io

Post reply on HN
Print view View original

101–110 of 193 posts

Re: How I use every Claude Code feature

#101

Post by michaelbuckbee »

WA wrote: post #98
michaelbuckbee wrote: post #95

Earlier quoted context omitted.

The prerequisite thought here is that you're using CC to invoke CLI tools. So now you need to get CC to understand _how_ to do that for various tools in a way that's context efficient, because otherwise you're relying on either potentially outdated knowledge that Claude has built in (leading to errors b/c CC doesn't know about recent versions) or chucking the entirety of a man page into your default context (ineffice…

After CC used that skill and it is now in the context, how do you get rid of it later when you don’t need the skill anymore and don’t want to have your context stuffed with useless skill descriptions?

You'd need to do the "/clear" or other context manipulations.

Re: How I use every Claude Code feature

#102

Post by mritchie712 »

> /clear + /catchup (Simple Restart): My default reboot. I /clear the state, then run a custom /catchup command to make Claude read all changed files in my git branch.

I've found myself doing similar workarounds. I'm guessing anthropic will just make the /compact command do this instead soon enough.

Re: How I use every Claude Code feature

#103

Post by rglover »

MangoToupe wrote: post #40

Blog posts like this would really benefit from specific examples. While I can get some mileage out of these tools for greenfield projects, I'm actually shocked that this has proven useful with projects of any substantial size or complexity. I'm very curious to understand the context where such tools are paying off.

It seems to be relative to skill level. If you're less-experienced, you're letting these things write most if not all of your code. If you're more experienced, that's inverted (you write most of the code and let the AI safely pepper things in).

Re: How I use every Claude Code feature

#104

Post by dlojudice »

sshh12 wrote: post #52
dfabulich wrote: post #36

> If you’re not already using a CLI-based agent like Claude Code or Codex CLI, you probably should be. Are the CLI-based agents better (much better?) than the Cursor app? Why? I like how easy it is to get Cursor to focus a particular piece of code. I select the text and Cmd-L, saying "fix this part, it's broken like this ____." I haven't really tried a CLI agent; sending snippets of code by CLI sounds really annoying…

Yeah I started with Cursor, went hybrid, and then in the last month or so I've totally swapped over. Part of it is the snappy more minimal UX but also just pure efficacy seems consistently better. Claude does its best work in CC. I'm sure the same is true of Codex.

Cursor Composer appears to have this type of coupling and uses IDE resources better than other models on average.

Re: How I use every Claude Code feature

#105

Post by reachableceo »

swah wrote: post #91
ed_mercer wrote: post #70

Earlier quoted context omitted.

My m1 macbook pro works fine with +10 claude code sessions open at the same time (iTerm2). Are you using a terminal with a memory leak perhaps?

How are you managing 10 parallel agents??

I use Windows Terminal. Rename tab.

My current project I have a top level chat , then one chat in each of the four component sub directories.

I have a second terminal with QA-feature

So 10 tabs total . Plus I have one to run occasional commands real quick (like docker ps).

I’m using qwen.

Re: How I use every Claude Code feature

#106

Post by exasperaited »

larusso wrote: post #74
phplovesong wrote: post #59

No thanks. I rather write the code myself that use generated slop. I actually like to code and see little benefit in other peoples copypaste code (thats essentially what ai slop is really)

I feel or have the fear that the world will tumble and crack under the sheer amount of code we produce and can’t be maintained because at one point no one human can understand all the stuff that was written. At the moment though I also code on and off with an agent. I’m not ready or willing to only vibe code my projects. For one is the fact that I had tons of examples where the agent gaslighted me only to turn around…

> I feel or have the fear that the world will tumble and crack under the sheer amount of code we produce and can’t be maintained because at one point no one human can understand all the stuff that was written.

IMO the best advice in life is try not to be fearful of things that happen to everyone and you can't change.

Good news! What you are afraid of will happen, but it'll happen to everyone all at once, and nothing you can do can change it.

So you no longer need to feel fear. You can skip right on over to resignation. (We have cookies, for we are cooked)

Re: How I use every Claude Code feature

#107

Post by maddmann »

I really enjoyed reading this. One thought I had on the issue of paths in Claude.md

My concern with hardcoding paths inside a doc, it will likely become outdated as the codebase evolves.

One solution would be to script it and have it run pre commit to regenerate the Claude.md with the new paths.

There probably is potential for even more dev tooling that 1. Ensure reference paths are always correct, 2. Enforces standard for how references are documented in Claude.md (and lints things like length)

Perhaps using some kind of inline documentation standard like jsdoc if it’s a ts file or a naming convention if it’s an Md file

Example:

// @claude.md // For complex … usage or if you encounter a FooBarError, see ${path} for advanced troubleshooting steps

Re: How I use every Claude Code feature

#108

Post by maddmann »

ed_mercer wrote: post #68

I don't understand how people use the `git worktree` workflow. I get that you want to isolate your work, but how do you deal with dev servers, port conflicts and npm installs? When I tried it, it was way more hassle than it was worth.

Yeah it is a mystery to me how folks could also maintain context in more than two sessions. The code review would be brutal.

You’ll also end up dealing with merge conflicts if you haven’t carefully split the work or modularized the code.

Re: How I use every Claude Code feature

#109

Post by risyachka »

brabel wrote: post #93
risyachka wrote: post #73

Earlier quoted context omitted.

>> Why are you producing so much code? This is basically a "thinking tax". If you don't want to think and offload it to llm they burn through a lot of tokens to implement in a non-efficient way something you could often do in 10 lines if you though about it for a few minutes.

I’ve just implemented a proof of concept that involved an API, a MCP server, an Authorization Server, a React frontend, token validation and proof of possession on the client, a CIBA flow for authentication… took a week , and I don’t even know the technologies used very well, it was all TypeScript but I work on JVM languages normally. This was a one off for a customer and I was able to show a fairly complex workflow…

>> I don’t even know the technologies used very well

Thats why it took a week with llm. And for you it makes sense as this is new tech.

But if someone knows those technologies - it would still take a week with llm and like 2 days without.

Re: How I use every Claude Code feature

#110

Post by kristofferR »

sshh12 wrote: post #52
dfabulich wrote: post #36

> If you’re not already using a CLI-based agent like Claude Code or Codex CLI, you probably should be. Are the CLI-based agents better (much better?) than the Cursor app? Why? I like how easy it is to get Cursor to focus a particular piece of code. I select the text and Cmd-L, saying "fix this part, it's broken like this ____." I haven't really tried a CLI agent; sending snippets of code by CLI sounds really annoying…

Yeah I started with Cursor, went hybrid, and then in the last month or so I've totally swapped over. Part of it is the snappy more minimal UX but also just pure efficacy seems consistently better. Claude does its best work in CC. I'm sure the same is true of Codex.

Seems you haven't heard of Cursor 2.0

https://cursor.com/blog/2-0

Post reply on HN