Just read it and the author say "do not use NEVER" in claude.md then in his sample claude.md there is NEVER the word, am I missing something?
How I use every Claude Code feature
181–190 of 193 posts
Re: How I use every Claude Code feature
#182Re: How I use every Claude Code feature
#183Earlier quoted context omitted.
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.
That's a lot of cognitive load to manage especially with how fast CC has become, do you review the output at all?
Re: How I use every Claude Code feature
#184We are literally having to play mind games with our tooling now to convince and coax it into doing certain things. I swear we are not far off from having to call in sick to work because your LLM "is going through a lot right now and just needs a mental health break".
Re: How I use every Claude Code feature
#185Man, I just want to point out how different programming has become in 2 years. We are literally having to play mind games with our tooling now to convince and coax it into doing certain things. I swear we are not far off from having to call in sick to work because your LLM "is going through a lot right now and just needs a mental health break".
I just don't wanna deal with any of this.
Re: How I use every Claude Code feature
#186At this point these tools are all pretty good. I also feel like folks often also over index on the output style or UI. Like to me the “you’re absolutely right!” sycophancy isn’t a notable bug; it’s a signal that you’re too in-the-loop. Generally my goal is to “shoot and forget”—to delegate, set the context, and let it work. Judging the tool by the final PR and not how it gets there. I use LLM tools daily and my exper…
Re: How I use every Claude Code feature
#187Earlier quoted context omitted.
I have the same instinctive response to reading AI generated stuff, but I'm coming to a more moderate position where I'm trying to judge the content on the content itself. For example, in a post like this, it doesn't bother me at all because it's still an extremely useful reference, and the author clearly read through, organized, and edited the output. This is a good example of usage of AI in my opinion. The people w…
Writing is a tool for thought I feel, and when you're outsourcing your thought, it detracts from whatever you intended to say. I guess if it was that heavily-edited such a telltale sign wouldn't have remained. I use AI for code, but I never use it for any writing that is for human eyes.
Re: How I use every Claude Code feature
#188Earlier quoted context omitted.
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.
MCPs still lack scoping in most cases. It's not that practical to have an MCP that can connect to, for example, ALL of your corporate Google Drive. Not happening. Why isn't it possible to limit it to a specific whitelisted set?
It is but you need to use an MCP client and servers that implement Roots.
Re: How I use every Claude Code feature
#189Are "agents" really as useful as the hype makes them out to be? Most of the time I'm just pasting code blocks directly into raycast and once I've fixed the bug or got the properly transformed code in the shape that I aimed for, then I paste it back into neovim. Next i'm going to try out "opencode"[0], because I've heard some good things about it. For now, I'm happy with my current workflow. [0] https://github.com/Nic…
Re: How I use every Claude Code feature
#190Blog 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).
But I dunno. I kind of wonder how I would have acted with tech like this available when I first started years ago. As a young engineer and even now I live and breathe the code, obsessing over testing and all the thing that make software engineering so fun. But I can't say whether or not I would have overdepended on an LLM as a young engineer.
It's all kind of depressing IMO, but it is what it is at this point.