Why would I trust my data to a vibe coded database, over a battle tested, tested to hell and back one?

dekelpilli a day ago | parent | next [-]

Dolt has been around for 7 years[0]. Doltlite, like most software nowadays, has been touched by LLMs, but dismissing this project as "vibe coded" seems harsh

[0] - https://www.dolthub.com/blog/2019-10-14-dolt-a-simple-exampl...

▲

asaddhamani a day ago | parent | next [-]

It is vibe coded.

But worse.

> Gas Town is for “write-only code”, … If you adopt Gas Town, you will lose the speed benefit of multiple agents if you read the code it produces. The first time you stare at an 8,500 line Git diff and try and parse what happened, you’ve lost. Go back to a single Claude Code session. Gas Town isn’t for you.

So none of the code has even been read by the author, it’s purposely overly verbose. “Touched by LLMs” seems to downplay just how vibe coded this is. I won’t use this database for anything.

▲

Skinney a day ago | parent | prev | next [-]

> Doltlite, like most software nowadays, has been touched by LLMs, but dismissing this project as "vibe coded" seems harsh

From the article, at the end of the second paragraph:

> Could a team of agents pull it off? It only took about 2,000 pull requests but DoltLite going Beta proves a team of agents certainly could.

The first PR was merged March 17th.

"vibe coded" seems pretty fitting

▲

solarkraft a day ago | parent [-]

If going through a strongly designed process with quality gates is vibe coding, I guess so. I thought the term was reserved fir “claude, make this happen” style development and the term for the more professional approach was “agentic development”, though this seems to be another layer higher.

Grouping it all under “vibe coded” loses precision. Sure, it uses AI, but differently from other projects and with different implications.

	▲	louis-lau 20 hours ago \| parent [-]
		Agentic development still requires human review and human ownership of PRs. This is vibe coded. Seems precise to me.

▲

leouno 16 hours ago | parent | prev [-]

[dead]

▲

rurban a day ago | parent | prev | next [-]

Battle tested and tested to hell, maybe yes. But still horrible insecure architecture, with read-only access being able to write. And totally insecure full text search. https://github.com/rurban/hardsqlite

▲

throw234259 a day ago | parent | prev [-]

Look at dev process (i did), this think is "tested to hell" and "battle tested".

But the feedback loop was automated and accelerated. Instead of 1000 loops spread over 20 years, it had 1000 loops over a few months.

Calling it "vibe coded" just shows something about you, not the project. It is not production ready yet, but that is not for fast ai dev or for technical reasons. It needs independent reviews, independent verification, and reputation.

▲

postexitus a day ago | parent | next [-]

This, from a 1 day old throwaway account, tells a lot.

▲

grebc a day ago | parent | prev | next [-]

Battle tested means deployed in production.

So when you say battle tested earlier, and then not production ready later - which one is it?

▲

esperent a day ago | parent | next [-]

That's selling it short. You could deploy something to production in minutes. Battle tested implies it's been not only deployed, but heavily used in all kinds of scenarios, and in the case of sqlite, probably by millions of different apps.

But anyway I assume that random name green account above is just a pro-vibe coding bot.

	▲	grebc 21 hours ago \| parent [-]
		It’s ridiculous how common the bots are becoming, then again Sam’s put a lot of money on the line so can’t be having bad vibes.

▲

a day ago | parent | prev [-]

[deleted]

▲

vrighter a day ago | parent | prev [-]

I don't trust AI testing. An automated loop == zero testing in my book.