←back to thread

Building a Personal AI Factory

(www.john-rush.com)
260 points derek | 5 comments | | HN request time: 0.715s | source
1. photon_garden ◴[] No.44438401[source]
It’s hard to evaluate setups like this without knowing how the resulting code is being used.

Standalone vibe coded apps for personal use? Pretty easy to believe.

Writing high quality code in a complex production system? Much harder to believe.

replies(2): >>44438831 #>>44439142 #
2. kasey_junk ◴[] No.44438831[source]
I don’t really understand this article or the workflow it’s describing as it’s kind of vague.

But I use multiple agents talking to each other, async agents, git work trees etc on complex production systems as my day to day workflow. I wouldn’t say I go so far as to never change the outputs but I certainly view it as signal when I don’t get the outputs I want that I need to work on my workflow.

3. 9cb14c1ec0 ◴[] No.44439142[source]
Exactly. I use claude code as a major speedup in coding, but I stay in the loop on every code change to make sure it is creating an optimal system. The few times that I've just let it run have resulted in bugs that customers had to deal with.
replies(2): >>44440091 #>>44440755 #
4. Aeolun ◴[] No.44440091[source]
I think you can probably get a pretty decent thing going if you have models review output they haven’t written themselves (not still in context anyway)
5. stpedgwdgfhgdd ◴[] No.44440755[source]
I noticed that i hardly look anymore at the generated Go code… I do give a lot of attention to the tests. I let CC write some failing tests, implement. Let it run against some real scenarios. Find bugs, let it write more tests, fix. And iterate.

Writing this I realise, i should more clearly separate the functional tests from the implementation oriented unit tests.