271–280 of 464 posts
Dang! Glad to see others doing this. I totally made this site yesterday like 11 hours ago :/ but did not get the traction. I love your implementation. Here was my first stab: https://news.ycombinator.com/item?id=47595140 https://brandonrc.github.io/journey-through-claude-code/
Even today, I'm still astounded that there are people capable of building a gorgeous and interesting site like this in less than 2 days...
I know it seems counter-intuitive but are there any agent harnesses that aren’t written with AI? All these half a million LoC codebases seem insane to me when I run my business on a full-stack web application that’s like 50k lines of code and my MvP was like 10k. These are just TUIs that call a model endpoint with some shell-out commands. These things have only been around in time measured in months, half a million L…
Earlier quoted context omitted.
It's only 510k LoC, at ~100 lines of code a day for a year, this code base would take 23 engineers a year to write. That's for 220 working days in somewhere civilized. And I'm sure we all know that when working on a greenfield project you can produce a lot more LoC per day than maintaining a legacy one. Given that vibe code is significantly more verbose, you're probably talking about ~15 engineers worth of code? I kn…
When you say it’s not a massive codebase, I’m curious, what are you comparing it to?
Earlier quoted context omitted.
> Claude Code's 500k LOC doesn't seem out of the ordinary. Aren't all the other products also vibe-coded? "All vibe-coded products look like this" doesn't really seem to answer the question "Why is it so damn large?" It's a repl, that calls out to a blackbox/endpoint for data, and does basic parsing and matching of state with specific actions. I feel the bulk of those lines should be actions that are performed. Eithe…
You're complaining about vibe coding while also complaining about how you "feel" about the code. Do you see the irony in that?
A 500k line codebase for an agent CLI proves one thing: making a probabilistic LLM behave deterministically is a massive state-management nightmare. Right now, they're great for prompting simple sites/platforms but they break at large enterprise repos. If you don't have a rigid, external state machine governing the workflow, you have to brute-force reliability. That codebase bloat is likely 90% defensive programming;…