I'm using Claude all the time now. It works, and I'm amazed it worked so easily for me. Here's what it looks like:

1) Summarize what I think my project currently does

2) Summarize what I think it should do

3) Give a couple of hints about how to do it

4) Watch it iterate a write-compile-test loop until it thinks it's ready

I haven't added any files or instructions anywhere, I just do that loop above. I know of people who put their Claude in YOLO mode on multiple sessions, but for the moment I'm just sitting there watching it.

Example:

"So at the moment, we're connecting to a websocket and subscribing to data, and it works fine, all the parsing tests are working, all good. But I want to connect over multiple sockets and just take whichever one receives the message first, and discard subsequent copies. Maybe you need a module that remembers what sequence number it has seen?"

Claude will then praise my insightful guidance and start making edits.

At some point, it will do something silly, and I will say:

"Why are you doing this with a bunch of Arc<RwLock> things? Let's share state by sharing messages!"

Claude will then apologize profusely and give reasons why I'm so wise, and then build the module in an async way.

I just keep an eye on what it tries, and it's completely changed how I code. For instance, I don't need to be fully concentrated anymore. I can be sitting in a meeting while I tell Claude what to do. Or I can be close to falling asleep, but still be productive.

▲

abraxas 2 days ago | parent [-]

I tried to follow the same pattern on a backend project written in Python/FastAPI and this has been mostly a heartache. It gets kind of close but then it seems to periodically go off the rails, lose its mind and write utter shit. Like braindead code that has no chance of working.

I don't know if this is a question of the language or what but I just have no good luck with its consistency. And I did invest time into defining various CLAUDE.md files. To no avail.

▲

ryandrake 2 days ago | parent | next [-]

What I find helpful in a large project is whenever Claude goes way off the rails, I correct it, and then tell it to update CLAUDE.md with instructions in its own words how to not do it again in the future. It doesn't stop the initial hallucinations and brainfarts, but it seems to be making the tool slowly better as it adds context for itself.

▲

lordnacho 2 days ago | parent | prev | next [-]

Has this got anything to do with using a stronger typed language? I've heard that reported, not sure whether it's true since my python scripts tend to be short.

Does it end in a forever loop for you? I used to have this problem with other models.

	▲	adastra22 2 days ago \| parent [-]
		I also use Rust with Claude Code, like GP. I do not experience forever loops — Claude converges on a working compiling solution every time. Sometimes the solution is garbage, and many times it gets it to “work” by disabling the test. I have layers of scaffolding (critic agents) that prevent this from being something I have to deal with, most of the time. But yeah, strongly typed languages, test driven development, and good high quality compiler errors are real game changers for LLM performance. I use Rust for everything now.

▲

wg0 2 days ago | parent | prev [-]

I can second that. Even on plain CRUD with little to no domain logic.