3 ms·

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

dekelpilli 25d ago
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-example/ https://www.dolthub.com/blog/2019-10-14-dolt-a-simple-exampl...
- Skinney 25d ago
  > 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 25d ago
    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 25d ago
      Agentic development still requires human review and human ownership of PRs. This is vibe coded. Seems precise to me.
      - zachmu 24d ago
        You can call it what you want I guess, but "vibe coded" around these parts is a simple pejorative, it means the authors don't know what the code does and the product is poor quality. Most successful agent-coded projects have a few essential features that it's worth calling out: 1) The human driving it has real domain expertise; 2) There's an oracle for correctness; 3) The agent has a real-world example to copy, adapt, or translate. This project had all these elements. The human driving the agent understood the technical and product decisions that make a version-controlled database work, because he's been doing that for 8 years. The project uses the existing 5.7M query test suite for SQLite3 as its oracle, as well as adapted versions of Dolt's extensive test suite to verify the version-control features that SQLite has no tests for. And the agent had a human-written implementation of the core product (Dolt) to crib from. All of this is to say: yes, agents wrote this code, but if you or another randomly chosen software engineer sat down and tried to duplicate this result you wouldn't succeed. You wouldn't know what the agent had gotten wrong at every step of development, or even what questions to ask to find out where the errors might be. Despite the existence of a correctness oracle, the agent on its own cannot iterate to 100% correctness without a domain expert steering it. And that expert also has to have an extensive understanding of the existing code base that's being copied. You can't just say "Claude, implement version control in SQLite3, make no mistakes", it's not going to work.
        killix 23d ago
        [flagged]
  - vrighter 23d ago
    "going beta" is a human decision. It proves nothing. All it proves is that at some point someone looked at it and said "good enough, ship it". It says nothing about the quality of the unreviewed code.
- asaddhamani 25d ago
  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.
- leouno 25d ago
  [dead]
throw234259 25d ago
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.
- grebc 25d ago
  Battle tested means deployed in production. So when you say battle tested earlier, and then not production ready later - which one is it?
  - deleted 25d ago
    [deleted]
  - esperent 25d ago
    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 25d ago
      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.
- postexitus 25d ago
  This, from a 1 day old throwaway account, tells a lot.
- vrighter 25d ago
  I don't trust AI testing. An automated loop == zero testing in my book.
rurban 25d ago
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 https://github.com/rurban/hardsqlite

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-example/ https://www.dolthub.com/blog/2019-10-14-dolt-a-simple-exampl...

Skinney 25d ago
> 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 25d ago
  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 25d ago
    Agentic development still requires human review and human ownership of PRs. This is vibe coded. Seems precise to me.
    - zachmu 24d ago
      You can call it what you want I guess, but "vibe coded" around these parts is a simple pejorative, it means the authors don't know what the code does and the product is poor quality. Most successful agent-coded projects have a few essential features that it's worth calling out: 1) The human driving it has real domain expertise; 2) There's an oracle for correctness; 3) The agent has a real-world example to copy, adapt, or translate. This project had all these elements. The human driving the agent understood the technical and product decisions that make a version-controlled database work, because he's been doing that for 8 years. The project uses the existing 5.7M query test suite for SQLite3 as its oracle, as well as adapted versions of Dolt's extensive test suite to verify the version-control features that SQLite has no tests for. And the agent had a human-written implementation of the core product (Dolt) to crib from. All of this is to say: yes, agents wrote this code, but if you or another randomly chosen software engineer sat down and tried to duplicate this result you wouldn't succeed. You wouldn't know what the agent had gotten wrong at every step of development, or even what questions to ask to find out where the errors might be. Despite the existence of a correctness oracle, the agent on its own cannot iterate to 100% correctness without a domain expert steering it. And that expert also has to have an extensive understanding of the existing code base that's being copied. You can't just say "Claude, implement version control in SQLite3, make no mistakes", it's not going to work.
      - killix 23d ago
        [flagged]
- vrighter 23d ago
  "going beta" is a human decision. It proves nothing. All it proves is that at some point someone looked at it and said "good enough, ship it". It says nothing about the quality of the unreviewed code.
asaddhamani 25d ago
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.
leouno 25d ago
[dead]

throw234259 25d ago

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.

grebc 25d ago
Battle tested means deployed in production. So when you say battle tested earlier, and then not production ready later - which one is it?
- deleted 25d ago
  [deleted]
- esperent 25d ago
  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 25d ago
    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.
postexitus 25d ago
This, from a 1 day old throwaway account, tells a lot.
vrighter 25d ago
I don't trust AI testing. An automated loop == zero testing in my book.

rurban 25d ago

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 https://github.com/rurban/hardsqlite