If Claude Code LLMs are reportedly so good, then why is the Claude Code CLI such a buggy, messy, featureless disaster? Are they dogfooding?
Eesh, a disaster? I use it daily to do some pretty impressive things. Wouldn’t call it a disaster.
Claude Code Checkpoints
21–30 of 136 posts
Re: Claude Code Checkpoints
#22This is something I really wish was just built-in to Claude Code. I want it built in because I don't want to have to think about it beforehand. I should be able to jump back in conversation history and have the state of the code jump back with me, so it's restored to the same state it originally was at that point in the conversation. (There does also need to be a way to jump back in the conversation history without r…
This was a pain point in coming from Aider to CC. How to have diffs of the changes once CC has done the changes? Having git commits done the way Aider does it would have saved me a lot of time.
You can prompt claude code to do that, or use hooks. You can run lint/test/commit automatically on agent stop.
Re: Claude Code Checkpoints
#23If Claude Code LLMs are reportedly so good, then why is the Claude Code CLI such a buggy, messy, featureless disaster? Are they dogfooding?
This is a funny comment because it's just made up
Re: Claude Code Checkpoints
#24i love the process of AI vibe coding slowly re-inventing the normal structures of software development how long until we start seeing software products for scrum management and t-shirt size estimation for claude code introduce waterfall methodology to the LLM!
T shirt estimation doesn't make any sense for AI dev, not one bit. They get epic long features done in hours, and all the shirt sizing comes from cases where the agent circles the drain and needs to be guided, which isn't predictable.
The shirt sizes now are for manual acceptance testing.
Re: Claude Code Checkpoints
#25I don't know what this is but isn't git enough? Incidentally I'm not convinced in my day-to-day for "jujitsu" (jj) but from what I understand about how it works, I've been wanting to give it a try for agent-based coding, based on the way it defaults to saving everything and letting you sort it out after. I do like how Aider commits everything so you can easily roll back, although it ends up with a few too many commit…
Git won't catch new files the agent is adding. To get around that you can of course always add all new files, but then you'll potentially have your repo polluted with a bunch of temporary scratch files instead. You can typically go back and edit git history. But it will require force push and breaking changes. And a few sacrifices to ensure that it doesn't make a mistake because then your repo is potentially broken.…
> Git won't catch new files the agent is adding.
Another problem I inadvertently dodged by using Jujutsu with Claude Code :)
I tend to send a lone "commit" message to Claude when I think I'm in a spot I may want to return to in the future, in case the current path doesn't work out. Then Claude commits it with a decent message. It knows how to use jj well enough for most things. Then it's really easy to jj new back to a previous change and try again.
Re: Claude Code Checkpoints
#26If Claude Code LLMs are reportedly so good, then why is the Claude Code CLI such a buggy, messy, featureless disaster? Are they dogfooding?
This is a funny comment because it's just made up
While disaster is strong language, Claude Code isn't really a well engineered product, they're just kinda trying shit, they don't have a clear long term vision. The core prompts and agent loop are good though, it's too bad it's not open source so someone could implement them in a client with good UX/engineering (at least without disassembling claude code and being legally questionable).
Re: Claude Code Checkpoints
#27i love the process of AI vibe coding slowly re-inventing the normal structures of software development how long until we start seeing software products for scrum management and t-shirt size estimation for claude code introduce waterfall methodology to the LLM!
T shirt estimation doesn't make any sense for AI dev, not one bit. They get epic long features done in hours, and all the shirt sizing comes from cases where the agent circles the drain and needs to be guided, which isn't predictable. The shirt sizes now are for manual acceptance testing.
My experience with AI tooling is that while it's really useful and great - I don't think i've ever seen a LLM complete an epic long feature well full stop.
Don't get me wrong, it's definitely improved my workflow and efficiency, but you must be winning at roulette if the model is performing well on anything that can't be googled and implemented witihn a similar amount of time.
unless it's claude, where even simple styling changes seem to become epics just when it wants to spit out an extra few thousands lines of code
Re: Claude Code Checkpoints
#28i love the process of AI vibe coding slowly re-inventing the normal structures of software development how long until we start seeing software products for scrum management and t-shirt size estimation for claude code introduce waterfall methodology to the LLM!
And soon enough it would need a project manager and HR to keep all the agents in line.
I hope the future becomes AI b2b sass agents selling b2b sass to other agents, just tools buying tools that in turn buy other tools ad infinitum
Re: Claude Code Checkpoints
#29Earlier quoted context omitted.
Git won't catch new files the agent is adding. To get around that you can of course always add all new files, but then you'll potentially have your repo polluted with a bunch of temporary scratch files instead. You can typically go back and edit git history. But it will require force push and breaking changes. And a few sacrifices to ensure that it doesn't make a mistake because then your repo is potentially broken.…
You could also create a branch, save your intermediates there, and then squash merge when you are ready.
Exactly. This is precisely what I do.
Re: Claude Code Checkpoints
#30[deleted]