Live data from Hacker News

How Anthropic teams use Claude Code

anthropic.com

221–230 of 248 posts

Re: How Anthropic teams use Claude Code

#221
post #99

Earlier quoted context omitted.

Have you seen human-written code?

At least when you tell a human the indentation is wrong, they can fix it on the first try. Watched an AI agent last night try to fix indentation by using sed for 20 minutes before I just fixed it myself after cringing.

Why the hell would anyone do this instead of using any one of dozens of purpose written tools that accept configuration files?

They take less than a second to run, can run on every save, and are free

Re: How Anthropic teams use Claude Code

#222

Earlier quoted context omitted.

I mean... this is a deterministic task, can just run it through autoformatter? Why ask AI to do indentation of all things?

One time I explained that I was afraid of tesla full self driving, because while using it my tesla accelerated to 45mph in a parking lot that was parallel to the road and only separated by a curb. The pushback I got was "Why would you use FSD in a parking lot". Well, "Full", right? Same here. It's either capable of working unsupervised or not. And if not, you have to start wondering what you're even doing if you're a…

A parking lot is an excellent use of self driving.

First, I want to summon my car. Then, when leaving, if I’m in a dense area with lots of shopping, the roads can be a pain. You have to exit right, immediately get into the left lane, three lanes over, the second of the right turn only lanes, etc

Re: How Anthropic teams use Claude Code

#224
post #62

My optimization hack is that I'm using speech recognition now with Claude Code. I can just talk to it like a person and explain the full context / history of things. Way faster than typing it all out.

any options for ubuntu ?

as above, open source and cross platform, should work on Ubuntu

https://handy.computer

Re: How Anthropic teams use Claude Code

#225
post #158

Earlier quoted context omitted.

Llms only work in one direction, they produce the next token only. It can't go back and edit. They would need to be able to back track and edit in place somehow

"Somehow", like caching multiple layers of context, like all the free tools are now doing?

That's different then seeing if it's current output made a mistake or not. It's not editing in place. Your just rolling the dice again with a different prompt

Re: How Anthropic teams use Claude Code

#226
post #146

Earlier quoted context omitted.

> Lack of iteration What makes you think that agents can't iterate? > I'm going to throw them out if they are just constantly showering me with praise and telling me how much of a genius I am You can tell the agent to have the persona of an arrogant ass if you prefer it.

> What makes you think that agents can't iterate? Please RTFA or RTF top most comment in the thread. Can they? Yes. Will they reliably? If so, why would it be better to restart... But the real answer to your question: personal experience

> Please RTFA

TFA says:

Engineers use Claude Code for rapid prototyping by enabling "auto-accept mode" (shift+tab) and setting up autonomous loops in which Claude writes code, runs tests, and iterates continuously.

The tool rapidly prototypes features and iterates on ideas without getting bogged down in implementation details

Re: How Anthropic teams use Claude Code

#227
post #158
post #146

Earlier quoted context omitted.

> Lack of iteration What makes you think that agents can't iterate? > I'm going to throw them out if they are just constantly showering me with praise and telling me how much of a genius I am You can tell the agent to have the persona of an arrogant ass if you prefer it.

Llms only work in one direction, they produce the next token only. It can't go back and edit. They would need to be able to back track and edit in place somehow

Loops.

Plus, the entire session/task history goes into every LLM prompt, not just the last message. So for every turn of the loop the LLM has the entire context with everything that previously happened in it, along with added "memories" and instructions.

Re: How Anthropic teams use Claude Code

#228
post #225

Earlier quoted context omitted.

"Somehow", like caching multiple layers of context, like all the free tools are now doing?

That's different then seeing if it's current output made a mistake or not. It's not editing in place. Your just rolling the dice again with a different prompt

No, the session history is all in the prompt, including the LLM's previous responses.

Re: How Anthropic teams use Claude Code

#229
post #228
post #225

Earlier quoted context omitted.

That's different then seeing if it's current output made a mistake or not. It's not editing in place. Your just rolling the dice again with a different prompt

No, the session history is all in the prompt, including the LLM's previous responses.

Appending more context to the existing prompt means it's a different prompt still... The text isn't the same

Re: How Anthropic teams use Claude Code

#230
post #229
post #228

Earlier quoted context omitted.

No, the session history is all in the prompt, including the LLM's previous responses.

Appending more context to the existing prompt means it's a different prompt still... The text isn't the same

I'm not sure what your point is?

Think of it like an append only journal. To correct an entry you add a new one with the correction. The LLM sees the mistake and the correction. That's no worse then mutating the history.

Post reply on HN