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

Claude Code 2.0

npmjs.com

Post reply on HN
Print view View original

181–190 of 431 posts

Re: Claude Code 2.0

#181

Post by 867-5309 »

Gigachad wrote: post #177
arjie wrote: post #89

I really like these tools. Yesterday I gave it a filename for a video of my infant daughter eating which I took while I had my phone on the charger. The top of the charger slightly obscured the video. I told it to crop the video to just her and remove the obscured portion and that I had ffmpeg and imagemagick installed and it looked at the video, found the crop dimensions, then ran ffmpeg and I had a video of her all…

Isn't cropping a video something you can do in the photos app in 2 seconds?

yeah, removing the unwanted item and keeping the video uncropped is surely more desirable, but far beyond the capabilities of "ai"

Re: Claude Code 2.0

#182

Post by stavros »

freedomben wrote: post #152
conception wrote: post #133

Earlier quoted context omitted.

You can rewind your context back to the checkpoint

That is nice, but it makes me wonder how little people actually know and use git nowadays. This is after all, something git really shines at. Still good to see! (It's not like I can't still just use git for that, which I fully intend to do)

I know and use git (well, Jujutsu, which is even better), but it's a right pain to figure out the time of each message and rewind to that exact point. The additional convenience is very much appreciated.

Re: Claude Code 2.0

#183

Post by adamckay »

rafaquintanilha wrote: post #35
jakozaur wrote: post #17

Just use `claude update` if you already have it. Unfortunately, they removed Plan mode, when I could use Opus for planning and Sonnect for coding. Though I will see how this pans out.

They removed the /model option where you can select Opus to plan and Sonnet to execute. But you can still Shift + Tab to cycle between auto-accept and plan mode.

You can use `/model opusplan` to get that behaviour back though if you do want Opus for planning and Sonnet for editing.

Re: Claude Code 2.0

#184

Post by bhl »

simonw wrote: post #49

Something I realized about this category of tool (I call them "terminal agents" but that already doesn't work now there's an official VS Code extension for this - maybe just "coding agents" instead) is that they're actually an interesting form of general agent . Claude Code, Codex CLI etc can effectively do anything that a human could do by typing commands into a computer. They're incredibly dangerous to use if you d…

Cursor will pivot to a computer use company.

The gap between coding agents in your terminal and computer agents that work on your entire operating system is just too narrow and will be crossed over quick.

Re: Claude Code 2.0

#185

Post by dota_fanatic »

spike021 wrote: post #128
turnsout wrote: post #108

Earlier quoted context omitted.

Yeah, I just have it generate PRDs/high-level plans, then break it down into cards in "Kanban.md" (a bunch of headers like "Backlog," "In-Progress", etc). To be honest, Claude is not great about moving cards when it's done with a task, but this workflow is very helpful for getting it back on track if I need to exit a session for any reason.

i've experienced the same thing. usually i try to set up or have it set up a milestone/phase approach to an implementation with checklists (markdown style) but it's 50/50 if it marks them automatically upon completion.

I have this in my CLAUDE.md and it works better than 50/50. Still not 100% though:

### Development Process

All work must be done via TODO.md. If the file is empty, then we need to write our next todo list.

When TODO.md is populated:

1. Read the entire TODO.md file first 2. Work through tasks in the exact order listed 3. Reference specific TODO.md sections when reporting progress 4. Mark progress by checking off todos in the file 5. Never abbreviate, summarize, or reinterpret TODO.md tasks

A TODO file is done when every box has been checked off due to completion of the associated task.

Re: Claude Code 2.0

#186

Post by dcreater »

ollysb wrote: post #155

The vscode integration does feel far tighter now. The one killer feature that Cursor has over it is the ability to track changes across multiple edits. With Claude you have to either accept or reject the changes after every prompt. With Cursor you can accumulate changes until you're ready to accept. You can use git of course but it isn't anywhere near as ergonomic.

Cline and it's forks have that in vs code. I use Cline with claude code as the LLM

Re: Claude Code 2.0

#187

Post by lihaciudanieljr »

gregable wrote: post #158
freedomben wrote: post #152

Earlier quoted context omitted.

That is nice, but it makes me wonder how little people actually know and use git nowadays. This is after all, something git really shines at. Still good to see! (It's not like I can't still just use git for that, which I fully intend to do)

There's value in rewinding both the code and the prompt to the some point in time.

[dead]

Re: Claude Code 2.0

#188

Post by teaearlgraycold »

bhl wrote: post #184
simonw wrote: post #49

Something I realized about this category of tool (I call them "terminal agents" but that already doesn't work now there's an official VS Code extension for this - maybe just "coding agents" instead) is that they're actually an interesting form of general agent . Claude Code, Codex CLI etc can effectively do anything that a human could do by typing commands into a computer. They're incredibly dangerous to use if you d…

Cursor will pivot to a computer use company. The gap between coding agents in your terminal and computer agents that work on your entire operating system is just too narrow and will be crossed over quick.

Once this tech is eliminating jobs on a massive scale I'll believe the AI hype. Not to say that couldn't be right around the corner - I have no clue. But being able to perform even just data entry tasks with better-than-human accuracy would be a huge deal.

Re: Claude Code 2.0

#189

Post by pancakemouse »

simonw wrote: post #49

Something I realized about this category of tool (I call them "terminal agents" but that already doesn't work now there's an official VS Code extension for this - maybe just "coding agents" instead) is that they're actually an interesting form of general agent . Claude Code, Codex CLI etc can effectively do anything that a human could do by typing commands into a computer. They're incredibly dangerous to use if you d…

Something I've seen discussed very little is that Claude Code can be opened in a directory tree of any type of document you like (reports, spreadsheets, designs, papers, research, ...) and you can play around in all sorts of ways. Anthropic themselves hint at this by saying their whole organisation uses it, but the `Code` moniker is probably limiting adoption. They could release a generalised agent with a friendlier UI tomorrow and get much wider workplace adoption.

Re: Claude Code 2.0

#190

Post by purerandomness »

navvyeanand wrote: post #176
ojosilva wrote: post #172

Earlier quoted context omitted.

Comments in code are instant technical debt. They need to be maintained alongside the code, so you are *programming" twice. Avoid comments, except when they really explain some obscure, incomprehensible section of code or to prevent explorers from the future getting smacked on the face twice by the same stick. I find myself using the latter often to tell future agents what not to do in the next few lines.

imo, comments are quite good for junior developers. docstrings are much preferred though.

Avoiding comments is an exercise in thinking how to rename or refactor a function, or a variable in such a way that a junior developer will be able to read it like prose, and immediately understand what's going on.

It's cognitively stressing, but is beneficial for juniors, and developers new to the codebase, just as it is for senior developers to reduce the mental overhead for the reader.

It's always good to spend an extra minute thinking how to avoid a comment.

Of course there are exceptions, but the mental exercise trying to avoid having that exception is always worth it.

Comments are instant technical debt.

Especially junior developers will be extremely confused and slowed down by having to read both, the comment, and then the code, which was refactored in the meantime and does the opposite of what the comment said.

Post reply on HN