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

You shouldn't copy-paste errors into Claude Code

home.robusta.dev

Post reply on HN
Print view View original

61–70 of 71 posts

Re: You shouldn't copy-paste errors into Claude Code

#61

Post by speakingmoistly »

nyellin wrote: post #56
aarjaneiro wrote: post #24

I wasn't expecting the answer to be "because copy-pasting would involve too much thinking". Some people are borderline afraid to touch their keyboards these days.

How does copy pasting an error into an LLM involve thinking?

At the very least, I would imagine you'd read and think about the error, parse through and clean it up for unneeded bits if the whole thing isn't relevant and write around it to provide context on what happened / possible things to correlate with it in case you have hypotheses to work out.

Re: You shouldn't copy-paste errors into Claude Code

#62

Post by voidfunc »

scrubs wrote: post #37
voidfunc wrote: post #27

Earlier quoted context omitted.

Hellscape? You mean money train! Fixing all these messes is gonna employ an industry of senior, principal and staff engineers for years.

Good lord! Since when did engineering become making crap then fixing crap as a flex? To just make payroll so some corporate robo moron can make rent? You cannot be in my team. Or my company. Willy nilly giving an agent more (write) access to figure out a bug ... man you're daydreaming.

You completely misunderstood what I was saying.

Re: You shouldn't copy-paste errors into Claude Code

#63

Post by bryanlarsen »

It's clear that Anthropic itself is following this bad advice. Cut and paste is broken in Claude Code -- anything it prints for you to cut and paste is markdown formatted, so cutting and pasting will end up with leading spaces and extraneous newlines.

This brokenness has persisted for at least a year.

WTF? There's a bloody good reason Claude doesn't have sudo access. Claude was useful for debugging the LVM mess I made, but its broken cut and paste was seriously frustrating.

Re: You shouldn't copy-paste errors into Claude Code

#64

Post by ignoramous »

QuercusMax wrote: post #32
danlitt wrote: post #9

I seriously thought this was a joke the first time I read it. Are people really able to work like this, understanding nothing and just poking the machine until it does your job for you?

I worked for most of a decade on an a high profile deep learning project and I sat next to people who trained models used for very complicated and interesting things involved in medicine. I built tons of application code around the models, but I never trained any models myself. I did plenty of old school segmentation stuff earlier in my career, and it just really wasn't my jam - I was much more into the visualization…

Amazing! Thanks for sharing.

> I didn't look at any of the code, but I had it build me a bunch of various visualization and tuning UIs. I was basically acting as a PM/TPM/QA engineer, and what I was able to do in a couple evenings is stuff that entire teams used to spend weeks on.

Agree. The pace of improvement (for coding tasks) from all Labs vying to catch up to the Big 3 (GDM, OAI, Ant) has been relentless.

> So I asked my agent (I'm using some free agents that are pretty decent - Nemotron Ultra from OpenRouter and Big Pickle from OpenCode Zen) to build me an OpenCV classifier to try to read the digits.

I think, Meta's Muse Spark is also free to use, for now. I'd be interesting if you'd ever find yourself using that.

If I may: Did you find Big Pickle is better than Nemotron Ultra or vice versa? Which harness (or IDE) did you drive these models with?

Re: You shouldn't copy-paste errors into Claude Code

#65

Post by aspbee555 »

nyellin wrote: post #54
aspbee555 wrote: post #10

Earlier quoted context omitted.

I was handed a project someone vibe coded with Claude and it took me hours just to get it running to discover it was missing the entire interface and all the queries were for sqlite while the DB to setup for it was mysql. The patch diff file between what claude produced and the functional version I got working was over 11k lines

I'm the OP and this is the exact point of the post. Whoever handed you that project did not have Claude code running it end to end in a production-like environment. Whether you like the vibe coded app or not, you would have had fewer errors if Claude had been testing it end to end while vibe coding.

definitely better when guided properly. Its like the old art of searching, if you gave it a good search query it would find what you were looking for. Same goes for AI now, how you prompt it makes all the difference

funny enough with my diff and directions even claude recognized how much a problem it created and what it would take to fix it

Re: You shouldn't copy-paste errors into Claude Code

#67

Post by anuramat »

asdff wrote: post #26
anuramat wrote: post #16

Earlier quoted context omitted.

he isn't wrong about the doctors though

Of course he is because even if the doctor typed like that, how would the patient see it? They don't do that in the exam room with the patient there. I wonder how long it's been since they've even had an appointment with their doctor if they think that is what actually happens.

> how would the patient see it

idk, I just know doctors who complained about the same thing for years

Re: You shouldn't copy-paste errors into Claude Code

#68

Post by anuramat »

interf4ce wrote: post #23
anuramat wrote: post #15

Earlier quoted context omitted.

if you can't tell if slop is correct, how do you know your code is correct? starting with a mental model and then writing the code yourself surely makes it feel safer, but it doesn't mean it is besides, it doesn't even have to be about writing code; finding a bug is more time consuming than fixing it, so you could at least limit yourself to that

When I write the code I know what my intention is with each line. Sure I can (and do) make mistakes, but identifying those mistakes during debugging is relatively easy during debugging because I can clearly see the discrepancy between what I intended and what I did. With an LLM I must first understand (usually really just infer and guess) its intention, which is much more difficult.

> much more difficult

as in time consuming or error prone?

if it's just time consuming, it still might be faster than writing it yourself

Re: You shouldn't copy-paste errors into Claude Code

#69

Post by QuercusMax »

ignoramous wrote: post #64
QuercusMax wrote: post #32

Earlier quoted context omitted.

I worked for most of a decade on an a high profile deep learning project and I sat next to people who trained models used for very complicated and interesting things involved in medicine. I built tons of application code around the models, but I never trained any models myself. I did plenty of old school segmentation stuff earlier in my career, and it just really wasn't my jam - I was much more into the visualization…

Amazing! Thanks for sharing. > I didn't look at any of the code, but I had it build me a bunch of various visualization and tuning UIs. I was basically acting as a PM/TPM/QA engineer, and what I was able to do in a couple evenings is stuff that entire teams used to spend weeks on. Agree. The pace of improvement (for coding tasks) from all Labs vying to catch up to the Big 3 (GDM, OAI, Ant) has been relentless. > So I…

I've been using OpenCode for hosted models, but pi-coder works better with the locally hosted models. I'm thinking of trying pi-coder in general because OpenCode doesn't handle retries as well as it could.

Big Pickle is really good, but I run out of my free OpenCode Zen quota pretty quickly. I used Claude a lot at work, and Big Pickle is right up there from what I've seen.

Nemotron Ultra on OpenRouter is nearly as good, but it's down a LOT, and it can sometimes be kinda dumb, and loves to gaslight me. I was arguing with it for a while yesterday because it was absolutely convinced it had fixed my bug and pushed to production, because it wasn't picking up on the issue I was describing, so clearly it was fixed!

Post reply on HN