kaydub

I've seen the bills at my org, I think the demand is there for now.

Our claude bills are rivaling our datadog bills and might get to the size of our AWS bills. It's pretty crazy.

The LLM is like the swiss army knife in these situations. It can KINDA do it all, but not very well in a lot of cases. Better to have specialized tools in most cases. And you're right, the LLM is pretty good for figuring out or building out the right tool for the job.

Cop stole house from dead man. Then cop sued company that rightfully bought house from dead man's heirs?

Except they didn't ban verbally abusive language towards its agents.

I hate when people put things in quotes as if they're quoting something but it's not even a quote of anything.

Maybe go read the user policy instead of the headlines and the snippets. If your attention span can't manage that, get off the computer a little bit.

Here's a good way to think about this.

If I have a business and I raise $10M at a $100M valuation for 10% of the company, the people giving me the money really value the business at $90M, their addition of the $10M into the business brings the valuation to $100M.

It's not always exactly like that, 1 for 1, but that's the gist. Without the capital, the business is not worth as much as the valuation at the time of the raise.

Only a couple of our repos hit the Ms, most are in the 100s of thousands of lines of code. Some in the 10s of thousands. But we're often working across multiple repos. Most everything is micro-services but we still have legacy monoliths that will be around forever probably. This is across hundreds of repos.

You haven't disproven shit using research papers using Claude 2

You know it's possible to READ too, right? I don't have to write the code or documentation... not that writing documentation means anything.

I have hundreds of repos at my job, some are in the 10s of thousands of lines of code, many are in the hundreds of thousands, and we still have a couple monoliths in the millions of lines of code range.

Personal projects completely built with the LLM range in the 10s to 100s of thousands of lines.

It's sustainable. LLMs have no problem working on all these projects and working on them across repos.

But I don't know what "vibe coding actual large projects blind" is supposed to mean.

This is a good list of things

I remember buying a lifetime VPS that was listed on LowEndBox for like $20. Can't remember the spec and I guess a lifetime means 5 years, but I couldn't complain for $20

Pre-llm I'd say it can be more undertaking than most people care to take to move to "serverless" or "cloud native" tech. But now it's probably worth taking a crack at it.

I don't miss sshing into servers or using puppet, ansible, salt, chef.

I don't use any cheap VPS providers. Everything is in AWS for me. I do run a single small ec2 instance ($8/mo?) that runs a personal mediawiki and a game server (for some multiplayer games I made).

I run a bunch of cheap (free?) custom apps for myself in the "serverless" or "cloud native" stuff in AWS. Everything else is on my NAS running on my home network (I see people mentioning qbittorrent, jellyfin, etc).

I stopped using cheap vps providers probably a decade ago, not a huge difference between a $5/mo cheap vps to a basic ec2 instance in pricing. And there were always issues with the cheap vps. Not to mention how easy it is to backup mediawiki + mysql in AWS vs having to spin up ANOTHER vps. Maybe there are cheap vps providers that offer object storage now, but I never bothered looking.

I'm arguing that the people doing this THINK it's saving tokens. I don't think it is. I've been seeing faster and more efficient use of the LLM by removing a lot of the documentation.

I'm not asking for anecdotes. I'm asking for actual real proof. I'm not the one making extraordinary claims about how my rube goldberg machine of documents and hacks works. I'm just using the tool as designed.

You're really going to use papers from 2023 and 2024? It's 2026. The models are better these days... a lot better. Like come on man "The best-performing model, Claude 2" You're going to base your assessment on THAT?

Dude, maybe it's YOU guys working on small codebases that are worrying about "knowing the codebase" or maybe you guys just work on shit code, I don't know. This industry isn't new, there are known patterns and the models know them. It's really not hard to navigate a new codebase if you know what you're doing or if you know the framework or patterns of the language/platform. If you think you know your whole codebase though, I'd argue that it's YOU working on a small or simple app.

I'm not even understanding your line of questioning here. I don't know the codebase because I had an LLM write it and I didn't write documentation? You think writing documentation means you know the codebase? You think having your goals in writing is any different than putting it in the prompt?

> But not as much of it since it has more context assuming the docs are good enough, which is my point.

Prove it.

Somewhat related, I DID test some of this stuff today. Plain claude, telling it to use gitlab mcp to review our codebase vs a big claude skill (for mr reviews) with a lot of details encoded in the plugin, kinda like these overly verbose and other llm generated document rube goldberg machine.

Plain claude with a simple paragraph prompt + gitlab mcp outperformed the skill by quite a bit. Less false positives, one finding the skill didn't find, ran in 4min for less than $1 vs 45min and $20 for the skill (which is basically overly verbose documentation packaged up)

The llms don't need your prose or your documentation, they can figure things out more efficiently without it.

> Are you writing any of the code? Writing the tests? If not, then there isn’t any proof that you actually know the code base unless you have documentation

The code is the documentation. You can read the code. This makes zero sense.

Your two statements are contradictory here. Docs should be good enough so the llm doesn't need to read the codebase, but it should just summarize everything? You can't have both.

I even stated in my OG post that I still keep a claude/agents.md, they're just VERY SMALL. I'm railing against the decision docs, the explosion of markdown files, and the extremely verbose code comments. All the LLM generated docs are causing friction more than anything, the llms are just good enough to work through it.

Yeah, I'm being a little extreme here and conflating a couple things.

You absolutely need some documentation. Like I originally said, I still do keep a claude/agents.md too, they're just stripped down A LOT.

Human maintained knowledge base and documentation is good. Not even 100% human maintained, just make sure human eyes are reading it before you commit it! And if it's said in code it doesn't need to also be said in the docs, that's how they get stale and you get drift. This is causing LLMs problems.

The docs you don't need are big decision docs that keep getting appended to, multiple long lived markdown files, and verbose comments (I literally saw multiple MRs today with more lines of comments than lines of code, as bad as one file that had a single line changed but then 5 paragraphs of mostly unrelated details, overly specific details, and just plain claude slop). This stuff isn't helping.

And the one issue I'm mainly conflating this with are all the skills/plugins/etc that people are making thinking it's making their claude better. Like the super-powers repo that's been floating around for months, that thing is trash, you don't need it. Maybe you did before (I still don't really think so) but you especially don't need it now.

One guy is talking about running tests and parsing json with claude... but why would you even do that? Just make deterministic tools and then you run those for your testing.

Again, something else I'm seeing, someone wedging claude into ci/cd and then having claude use skills that run linters and trivy. Why is that not just in ci/CD???

The proliferation of prose is maddening