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

Building a Personal AI Factory

john-rush.com

Post reply on HN
Print view View original

71–80 of 167 posts

Re: Building a Personal AI Factory

#71

Post by csomar »

simonw wrote: post #28

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 fract…

That's a very simple example/context that I suspect most LLMs will be able to knock out with minimal frustration. I had much more complex Rust dependency upgrade done on a 30+ iterations on very custom code (wasm stuff where training data is probably scarce). Claude would ping context7 and mcp-lsp to get details. You do find its limits after a while though and as you push it harder.

Re: Building a Personal AI Factory

#72

Post by steveklabnik »

Aeolun wrote: post #64
steveklabnik wrote: post #26

Earlier quoted context omitted.

It’s not about proof: it’s that at this point I’m a fairly heavy Claude Code user and I’d like to up my game, but I’m also not so up on many of these details that I can just figure out how to give this a try just from the description of it. I’m already doing plan-up-front workflows with just Claude, but haven’t figured out some of this more advanced stuff. I have two MCPs installed (playwright and context7) but it ne…

> I have two MCPs installed (playwright and context7) but it never seems like Claude decides to reach for them on its own. Not even when you add ‘memories’ that tell it to always use those tools in certain situations? My admonitions to always run repomix at the start of coding, and always run the build command before crying victory seem to be followed pretty well anyway.

I have not done that, maybe that's the missing bit. Thanks!

Re: Building a Personal AI Factory

#73

Post by nico »

csomar wrote: post #71
simonw wrote: post #28

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 fract…

That's a very simple example/context that I suspect most LLMs will be able to knock out with minimal frustration. I had much more complex Rust dependency upgrade done on a 30+ iterations on very custom code (wasm stuff where training data is probably scarce). Claude would ping context7 and mcp-lsp to get details. You do find its limits after a while though and as you push it harder.

> That's a very simple example/context that I suspect most LLMs will be able to knock out with minimal frustration

Yes an No. You are right that it's a relatively small project. However, I've had really bad experiences trying to get ChatGPT (any of their models) to write small arm64 assembly programs that can compile and run on apple silicon

Re: Building a Personal AI Factory

#74

Post by [deleted] »

marviel wrote: post #20

Thanks for the writeup! I talked about a similar, but slightly simpler workflow in my post on "Vibe Specs". https://lukebechtel.com/blog/vibe-speccing I use these rules in all my codebases now. They essentially cause the AI to do two things differently: (1) ask me questions first (2) Create a `spec.md` doc, before writing any code. Seems not too dissimilar from yours, but I limit it to a single LLM

[deleted]

Re: Building a Personal AI Factory

#75

Post by nico »

> If you know Factorio you know it’s all about building a factory that can produce itself

This is a very interesting concept

Could this be extended to the point of an LLM producing/improving itself?

If not, what are the current limitations to get to that point?

Re: Building a Personal AI Factory

#76

Post by 6510 »

cube00 wrote: post #40
geekymartian wrote: post #32

ADHD coding, brute forcing product generation until you get it right? Just freaking write the code that you can expand and modify in the future instead of increasing your carbon footprint.

The end goal is to remove the developer from this equation. Business owner asks for a new CRUD app and there it is in production. Of course it's full of full of bugs, slow as syrup, saves to a public unauthed database but that's none of my business *gulps scalding hot tea*

You have users fill out bug reports then throw some buckets of money at it.

You could even add a magic button for when things don't work that reruns the same prompt and possibly get better results.

A slot machine animation while waiting would be cool.

Re: Building a Personal AI Factory

#77

Post by [deleted] »

petesergeant wrote: post #45
apwell23 wrote: post #37

ppl are getting slowly disillusioned with vibe coding. yes AI assisted workflow might be here to stay but it won't be the magical put programmers out of job thing. And this the best product market fit for LLMs. I imagine it will be even worse in other domains.

> ppl are getting slowly disillusioned with vibe coding. This is the absolute polar opposite from my experience. I'm in a large non-tech community with a coders channel, and every day we get a few more Claude Code converts. I would say that vibe-coding is moving into the main-stream with experienced, professional developers who were deeply skeptical a few months ago. It's no longer fancy auto-complete: I have myself…

[deleted]

Re: Building a Personal AI Factory

#78

Post by manmal »

Aeolun wrote: post #64
steveklabnik wrote: post #26

Earlier quoted context omitted.

It’s not about proof: it’s that at this point I’m a fairly heavy Claude Code user and I’d like to up my game, but I’m also not so up on many of these details that I can just figure out how to give this a try just from the description of it. I’m already doing plan-up-front workflows with just Claude, but haven’t figured out some of this more advanced stuff. I have two MCPs installed (playwright and context7) but it ne…

> I have two MCPs installed (playwright and context7) but it never seems like Claude decides to reach for them on its own. Not even when you add ‘memories’ that tell it to always use those tools in certain situations? My admonitions to always run repomix at the start of coding, and always run the build command before crying victory seem to be followed pretty well anyway.

What do you tell Claude to do with repomix? Get an overview into the context?

Re: Building a Personal AI Factory

#79

Post by gen6acd60af »

fragmede wrote: post #54
simonw wrote: post #53

Earlier quoted context omitted.

I think the hardest problem in computer science right now may be coming up with an LLM demo that doesn't get called "pretty trivial".

I think Cloudflare's oauth library qualifies https://news.ycombinator.com/item?id=44159166

This one?

>Claude's output was thoroughly reviewed by Cloudflare engineers with careful attention paid to security and compliance with standards.

>To emphasize, this is not "vibe coded". Every line was thoroughly reviewed and cross-referenced with relevant RFCs, by security experts with previous experience with those RFCs.

Some time later...

https://github.com/advisories/GHSA-4pc9-x2fx-p7vj / CVE-2025-4143

>The OAuth implementation in workers-oauth-provider that is part of MCP framework https://github.com/cloudflare/workers-mcp, did not correctly validate that redirect_uri was on the allowed list of redirect URIs for the given client registration.

Re: Building a Personal AI Factory

#80

Post by stpedgwdgfhgdd »

ffsm8 wrote: post #67
zackify wrote: post #41

Earlier quoted context omitted.

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

you will run through the pro rate limiting within 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

Same experience. One terminal window with Pro is okay. Multiple CC running in parallel not.

We most likely implement a policy that starters in our company can use Pro. Power users need Max.

Post reply on HN