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
Building a Personal AI Factory
91–100 of 167 posts
Re: Building a Personal AI Factory
#92Earlier 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".
Re: Building a Personal AI Factory
#93Re: Building a Personal AI Factory
#94ADHD 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.
Re: Building a Personal AI Factory
#95Earlier quoted context omitted.
I keep coming to the same conclusion, which basically is: if I had an LLM write it for me, I just don't care about it. There are 2 projects out of the maybe 50 or so that are LLM generated, and even for those two I cared enough to make changes myself without an LLM. The rest just sit there because one day I thought huh wouldn't it be neat if, and then realized actually I cared more about having that thought than havi…
We just had a story last night about a Python cryptography maintainer using Claude to add formally-verified optimizations to LLVM. I think the ship has sailed on skepticism about whether LLMs are going to produce valuable code; you can follow Simon Willison's blog for more examples.
Re: Building a Personal AI Factory
#96Earlier 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".
Re: Building a Personal AI Factory
#97ppl 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…
In the end, it had written 500 lines, the problem was still there, and the code didn't work any differently. It worries me that I don't know what those 500 lines were for.
In my experience, LLMs are amazing for writing 10-20 lines at a time, while you review and fix any errors. If I let them go to town on my code, I've found that's an expensive way to get broken code.
Re: Building a Personal AI Factory
#98My 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…
Crack on - this is YC! Why are you not already a unicorn?
Re: Building a Personal AI Factory
#99And here I am struggling to get Claude to create a nice-looking search bar a la booking.com , with some adjustments for my personal use case; it does ok, but never gets to the end result and once I refreshed my Tailwind knowledge it felt much slower than hand coding. I feel like I'm living in a different world.
I guess keep them on backend/library tasks for now. I am sure the companies are already working on getting a snapshot of a browser page and feeding it back into multimodal model so it can comprehend what "looking" means.
Re: Building a Personal AI Factory
#100Earlier 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".
I'd say your mandelbrot debug and the LLVM patch are both "trivial" in the same sense: they're discrete, well defined, clear-success-criteria-tasks that could be assigned to any mid/senior software engineer in a relevant domain and they could chip through it in a few weeks.
Don't get me wrong, that's an insane power and capability of LLMs, I agree. But ultimately it's just doing a day job that millions of people can do sleep deprived and hungover.
Non-trivial examples are things that would take a team of different specialist skillsets months to create. One obvious potential reason why there's few non-trivial AI examples is because non-trivial AI examples require non-trivial amount of time to be able to generate and verify.
A non-trivial example isn't an example you can look at the output and say "yup, AI's done well here". It requires someone spends time going into what's been produced, assessing it, essentially redesigning it as a human to figure out all the complexity of a modern non-trivial system to confirm the AI actually did all that stuff correctly.
An in depth audit of a complex software system can take months or even years and is a thorough and tedious task for a human, and the Venn diagrams of humans who are thinking "I want to spend more time doing thorough, tedious code tasks" and "I want to mess around with AI coding" is 2 separate circles.