Just my curiosity: Why are you producing so much code? Is it because it is now possible to do so with AI, or because you have a genuine need (solid business usecase) that requires a lot of code?
How I use every Claude Code feature
41–50 of 193 posts
Re: How I use every Claude Code feature
#42> 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…
Yes and you can select multiple files to give it focus. It can run anything in your PATH too. Eg it's pretty good at using `gh` and so on
Re: How I use every Claude Code feature
#43Why are so many still using CC and not Codex
Ecosystem features and cohesion.
Re: How I use every Claude Code feature
#44Blog 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.
Makes sense. I work for a growth stage startup and most of these apply to our internal mono repo so hard to share specifics. We use this for both new and legacy code each with their own unique AI coding challenges.
If theres enough interest, I might replicate some examples in an open source project.
Re: How I use every Claude Code feature
#45I really like this take on MCP: https://blog.sshh.io/i/177742847/mcp-model-context-protocol > Instead of a bloated API, an MCP should be a simple, secure gateway that provides a few powerful, high-level tools [...] In this model, MCP’s job isn’t to abstract reality for the agent; its job is to manage the auth, networking, and security boundaries and then get out of the way.
Thanks! I def don't think I would have guessed this use case when MCP first came out, but more and more it seems Claude just yearns for scripting on data rather than a bunch of "tools". My/MCPs job has become just getting it that data.
Have you tried using light CLIs rather than MCP? I’ve found that CLIs are just easier for Claude, especially if you write them with Claude and during planning instruct it to think about adding guidance to users who get confused.
Our auth, log diving, infra state, etc, is all usable via cli, and it feels pretty good when pointing Claude at it.
Re: How I use every Claude Code feature
#46Just my curiosity: Why are you producing so much code? Is it because it is now possible to do so with AI, or because you have a genuine need (solid business usecase) that requires a lot of code?
I just started developing self-hosted services largely with AI.
It wasn't possible before for me to do any of this at this kind of scale. Before, getting stuck on a bug could mean hours, days, or maybe even weeks of debugging. I never made the kind of progress I wanted before.
Many of the things I want, do already exist, but are often older, not as efficient or flexible as they could be, or just plain _look_ dated.
But now I can pump out react/shadcn frontends easily, generate apis, and get going relatively quickly. It's still not pure magic. I'm still hitting issues and such, but they are not these demotivating, project-ending, roadblocks anymore.
I can now move at a speed that matches the ideas I have.
I am giving up something to achieve that, by allowing AI to take control so much, but it's a trade that seems worth it.
Re: How I use every Claude Code feature
#47> 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…
They all have optional ide integration, e.g Claude knows the active vscode tab and highlighted lines.
Is that better than Cursor? Same? Just different?
Re: How I use every Claude Code feature
#48> 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…
Claude is able to detect the lines of code selected in vscode anyway
Re: How I use every Claude Code feature
#49Just my curiosity: Why are you producing so much code? Is it because it is now possible to do so with AI, or because you have a genuine need (solid business usecase) that requires a lot of code?
Often code in SaaS companies like ours is indeed how we solve customer problems. It's not so much the amount of code but the rate (code per time) we can effectively use to solve problems/build solutions. AI, when tuned correctly, lets us do this faster than ever possible before.
Re: How I use every Claude Code feature
#50Earlier quoted context omitted.
Thanks! I def don't think I would have guessed this use case when MCP first came out, but more and more it seems Claude just yearns for scripting on data rather than a bunch of "tools". My/MCPs job has become just getting it that data.
Have you tried using light CLIs rather than MCP? I’ve found that CLIs are just easier for Claude, especially if you write them with Claude and during planning instruct it to think about adding guidance to users who get confused. Our auth, log diving, infra state, etc, is all usable via cli, and it feels pretty good when pointing Claude at it.
Yeah if that's possible or you are willing to build it, that's the right solution. Today pretty much all of my integrations are pure CLIs like that rather than MCPs.
You can do anything you want via a CLI but MCP still exists as a standard that folks and platforms might want to adopt as a common interface.