←back to thread

Building a Personal AI Factory

(www.john-rush.com)
260 points derek | 1 comments | 01 Jul 25 21:14 UTC | HN request time: 0.207s | source
Show context
simonw ◴[02 Jul 25 00:02 UTC] No.44439075[source]▶
My hunch is that this article is going to be almost completely impenetrable to people who haven't yet had the "aha" moment with Claude Code.

That's the moment when you let "claude --dangerously-skip-permissions" go to work on a difficult problem and watch it crunch away by itself for a couple of minutes running a bewildering array of tools until the problem is fixed.

I had it compile, run and debug a Mandelbrot fractal generator in 486 assembly today, executing in Docker on my Mac, just to see how well it could do. It did great! https://gist.github.com/simonw/ba1e9fa26fc8af08934d7bc0805b9...

replies(7): >>44439177 #>>44439259 #>>44439544 #>>44440242 #>>44441017 #>>44441069 #>>44441796 #
zackify ◴[02 Jul 25 00:38 UTC] No.44439259[source]▶
If it helps anyone else. I downgraded from Claude max to pro for $20 and the usage limits are really good.

I think they’re trying to compete with Gemini cli and now I’m glad I’m paying less

replies(2): >>44440204 #>>44440222 #
ffsm8 ◴[02 Jul 25 04:16 UTC] No.44440204[source]▶
you will run through the pro rate limiting within <1h if you do it the way the article lays out.

But yeah, if you're babysitting a single agent, only applying after reading what it wants to do ... You'll be fine for 3-4 hours before the token limit refreshed after the 5th

replies(2): >>44440718 #>>44440721 #
1. zxexz ◴[02 Jul 25 06:19 UTC] No.44440721[source]▶
I've heard that if you have several relatively active separate sessions open, the limit is a little less restrictive. Especially if you do a /clear and continue your session on a different project. Honestly, a lot of Claude Code seems vibecoded if you look at the client side, too. Can't tell if I'm surprised that the backend has an element of that, too. Hey, dogfood tastes good - I respect them for that.