Live data from Hacker News

What makes Claude Code so damn good

minusx.ai

71–80 of 322 posts

Re: What makes Claude Code so damn good

#71
post #63

Earlier quoted context omitted.

Overall I would agree with you, but I start feeling that this „iron law“ isn’t as simple as that. After all, humans have limited „context window“ too — we don’t remember every small detail on a large project we have been working on for several years. Loose coupling and modularity helps us and can help LLM to make the size of the task manageable if you don’t ask it to rebuild the whole thing. It’s not the size that ma…

Humans have a limited short-term memory. Humans do not literally forget everything they've ever learned after each Q&A cycle. (Though now that I think of it, I might start interrupting people with “SUMMARIZING CONVERSATION HISTORY!” whenever they begin to bore me. Then I can change the subject.)

LLMs do not „forget“ everything completely either. Probably all major tools by now consume information from some form of memory (system prompt, Claude.md, project files etc) before your prompt. Claude Code rewrites the Claude.md, ChatGPT may modify the chat memory if it finds it necessary etc.

Re: What makes Claude Code so damn good

#73

It shocks me when people say that LLMs don't make them more productive, because my experience has been the complete opposite, especially with Claude Code. Either I'm worse than then at programming, to the point that I find an LLM useful and they don't, or they don't know how to use LLMs for coding.

[deleted]

Re: What makes Claude Code so damn good

#74
I made insane progress with CC over last several weeks, but lately have noticed progress stalling.

I’m in the middle of some refactoring/bug fixing/optimization but it’s constantly running into issues, making half baked changes, not able to fix regressions etc. Still trying to figure out how to make do a better job. Might have to break it into smaller chunks or something. Been pretty frustrating couple of weeks.

If anyone has pointers, I’m all ears!!

Re: What makes Claude Code so damn good

#75

> "THIS IS IMPORTANT" is still State of the Art Had a similar problems until I saw the advice "Dont say what it shouldn't but focus on what it should". i.e. make sure when it reaches for the 'thing', it has the alternative in context. Haven't had those problems since then.

I mean, if advice like this worked, then why wouldn't Anthropic let the LLM say it, for instance?

Re: What makes Claude Code so damn good

#76
post #35

We’re considering building a coding agent for Lowdefy[1], a framework that lets you build web apps with YAML config. For those who’ve built coding agents: do you think LLMs are better suited for generating structured config vs. raw code? My theory is that agents producing valid YAML/JSON schemas could be more reliable than code generation. The output is constrained, easier to validate, and when it breaks, you can act…

> easier to validate This is essential to productivity for humans and LLMs alike. The more reliable your edit/test loop, the better your results will be. It doesn't matter if it's compiling code, validating yaml, or anything else. To your broader question. People have been trying to crack the low-code nut for ages. I don't think it's solvable. Either you make something overly restrictive, or you are inventing a very…

Good point. i’m making the assumption that if the LLM has a more limited feature space to produce as output, then the output is more predictable, and thus faster to comprehend changes. Similar to when devs use popular libraries, there is a well known abstraction, therefore less “new” code to comprehend as i see familiar functions, making the code predictable to me.

Re: What makes Claude Code so damn good

#77
post #63

Earlier quoted context omitted.

Humans have a limited short-term memory. Humans do not literally forget everything they've ever learned after each Q&A cycle. (Though now that I think of it, I might start interrupting people with “SUMMARIZING CONVERSATION HISTORY!” whenever they begin to bore me. Then I can change the subject.)

LLMs do not „forget“ everything completely either. Probably all major tools by now consume information from some form of memory (system prompt, Claude.md, project files etc) before your prompt. Claude Code rewrites the Claude.md, ChatGPT may modify the chat memory if it finds it necessary etc.

Writing stuff in a file is not “memory” (particularly if I have to do it), and in any case, it consumes context. Overrun the context window, and the tool doesn’t know about what is lost.

There are various hacks these tools take to cram more crap into a fixed-size bucket, but it’s still fundamentally different than how a person thinks.

Re: What makes Claude Code so damn good

#78

I don’t know if I’m doing something wrong. I was using Sonnet 4 with GitHub Copilot. Recently a week ago switched to Claude Code. I find GitHub Copilot solves problem and bugs way better than Claude Code. For some reason, Claude Code seems very lazy. Has anyone experience something similar?

I have most of the tools setup so I can switch between them and test which is better. So far Amp and Claude Code are on top. GH Copilot is the worst. I know MS is desperately trying to copy its competitors but the reality is, they are just copying features. They haven’t solved the system prompts. So the outcomes are just inferior.

Re: What makes Claude Code so damn good

#79
post #74

I made insane progress with CC over last several weeks, but lately have noticed progress stalling. I’m in the middle of some refactoring/bug fixing/optimization but it’s constantly running into issues, making half baked changes, not able to fix regressions etc. Still trying to figure out how to make do a better job. Might have to break it into smaller chunks or something. Been pretty frustrating couple of weeks. If a…

[dead]

Re: What makes Claude Code so damn good

#80
post #33

Oof, this comes at a hard moment in my Claude Code usage. I'm trying to have it help me debug some Elastic issues on Security Onion but after a few minutes it spits out a zillion lines of obfuscated JS and says: Error: kill EPERM at process.kill (node:internal/process/per_thread:226:13) at Ba2 (file:///usr/local/lib/node_modules/@anthropic-ai/claude-code/cli.js:506:19791) at file:///usr/local/lib/node_modules/@anthro…

[dead]
Post reply on HN