Live data from Hacker News

Building a Personal AI Factory

john-rush.com

121–130 of 167 posts

Re: Building a Personal AI Factory

#121
post #75

> 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?

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

Check out aider writing aider stats here: https://aider.chat/HISTORY.html

Re: Building a Personal AI Factory

#122
post #94

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.

Man, programming has changed forever, and the sooner you realize that, the better for you. Saying "write the code" is like telling people to shoe their own horses instead of dealing with them newfangled cars that can break down.

Didn't they say "programming has changed forever" about web3 stuff? I've not heard much about that recently

Re: Building a Personal AI Factory

#123
post #100
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'm very pro LLM and AI. But I completely agree with the comment about how many pieces praising LLMs are doing so with trivial examples. Trivial might not be the right word, but I can't think of a better one that doesn't have a negative connotation, but this shouldn't be negative. Your examples are good and useful, and capture a bunch of tasks a software engineer would do. I'd say your mandelbrot debug and the LLVM p…

I only see 148 lines of assembly and a dockerfile that's 7 lines long. Am I missing something or should that take a human less then several weeks.

Re: Building a Personal AI Factory

#124
post #97

Earlier quoted context omitted.

I don't doubt that LLMs are extremely useful for making simple things quickly. I haven't been able to get them to write hard code on their own, though. I was trying to make a sound card with a Pi Pico the other day, and had crackling and popping in the audio. I kept telling Opus to fix that, it kept being absolutely convinced it knows what the problem is every time, and went through multiple iterations of being absol…

> I haven't been able to get them to write hard code on their own, though For sure, and me neither, for what it's worth. But most of the code I write isn't "hard" code; the hard code is also the stuff I enjoy writing the most. I will note that a few months ago I found them helpful for small things inside the GPT window, and then tried agentic mode (specifically Roo, then Claude Code), and have seen a huge speedup in…

Agreed, I no longer have to write the same code for the Nth time, or spend two minutes times a hundred looking up API docs. I love it.

Re: Building a Personal AI Factory

#125
post #94

Earlier quoted context omitted.

Man, programming has changed forever, and the sooner you realize that, the better for you. Saying "write the code" is like telling people to shoe their own horses instead of dealing with them newfangled cars that can break down.

Didn't they say "programming has changed forever" about web3 stuff? I've not heard much about that recently

I don't know who "they" is, but I never said that.

Re: Building a Personal AI Factory

#126
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 pretty trivial example for one of these IDEs to knock out. Assembly is certainly in their training sets, and obviously docker is too. I've watched cursor absolutely run amok when I let it play around in some of my codebase. I'm bullish it'll get there sooner rather than later, but we're not there yet.

I suspect personal tools are as close as we're going to get to this mythical demo that satisfies all critics. i.e. here is a list of problems i've solved with just AI.

Strikes a balance between simplicity and real world usefulness

Re: Building a Personal AI Factory

#127
post #100

Earlier quoted context omitted.

I'm very pro LLM and AI. But I completely agree with the comment about how many pieces praising LLMs are doing so with trivial examples. Trivial might not be the right word, but I can't think of a better one that doesn't have a negative connotation, but this shouldn't be negative. Your examples are good and useful, and capture a bunch of tasks a software engineer would do. I'd say your mandelbrot debug and the LLVM p…

I only see 148 lines of assembly and a dockerfile that's 7 lines long. Am I missing something or should that take a human less then several weeks.

Depends on what's in those 148 lines.

Re: Building a Personal AI Factory

#128
> That loop is the factory: the code itself is disposable; the instructions and agents are the real asset.

Why do I hear the words "technical debt"? More to the point, the risk I see with this approach is that the author would end hp throwing away working and well tested code to implement some minor change. This has an high risk of introducing many easily avoidable bugs.

Re: Building a Personal AI Factory

#129
post #53

Earlier quoted context omitted.

That's a pretty trivial example for one of these IDEs to knock out. Assembly is certainly in their training sets, and obviously docker is too. I've watched cursor absolutely run amok when I let it play around in some of my codebase. I'm bullish it'll get there sooner rather than later, but we're not there yet.

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".

It coming from computer science might be the issue. There's a lot of open source repos out there that have tricky bugs, and todo lists of features that are too complex or time consuming for casual contributors to tackle. Adding significant value to an open source project is a pretty nice demo that won't get called "pretty trivial".

Can't be too far off!

Re: Building a Personal AI Factory

#130
post #53

Earlier quoted context omitted.

That's a pretty trivial example for one of these IDEs to knock out. Assembly is certainly in their training sets, and obviously docker is too. I've watched cursor absolutely run amok when I let it play around in some of my codebase. I'm bullish it'll get there sooner rather than later, but we're not there yet.

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".

The complexity of the problem masqerades the common problem of providing sensible context to your AI of choice to have it doing something constructive in your personal codebase. Or giving it tools to check the truth of one of its assertions. Something a developer does countless times.
Post reply on HN