Show HN: A vibe-coded database GUI(seaquel.app)
5 pointsby mootoday14 hours ago3 comments
  • mcbetz12 hours ago
    Article on the creation: https://www.mikenikles.com/blog/i-vibe-coded-a-database-gui

    Author wanted to try vibe coding, despite being a critic. Says that result is unmaintainable.

  • freakynit11 hours ago
    Cool product.. and looks excellent.. but...

    Did you just copied the tagline verbatim from my product: https://zenquery.app/ ?

    "Ask questions about your business data in plain English"

    • mcbetz8 hours ago
      The project was vibe-coded by the author and hence, likely the LLM created that tagline as well. Your service is around a year old (based on https://news.ycombinator.com/item?id=44321099) and LLMs might have picked it up already and also the tagline is straight forward business talk, so no big surprise that multiple people and LLMs come up with the same idea.
      • freakynit5 hours ago
        You have a point. There's high chance it might have become part of training data.

        Thanks..

    • mootoday5 hours ago
      Hey, I did not. As mcbetz mentioned, I tried vibe-coding and anything you see is generated by LLMs. He linked to my blog post where I summarized the journey.

      ZenQuery looks nice, I like the focus on supporting regular files.

      • freakynit5 hours ago
        No worries.. even if it were copied, it would have made me feel proud. Nevertheless, I saw it now that's its actually fully vibe-coded... so, high chance my product's webpage was part of it's training data..

        I did download your product ans using it for postgres. Was using dbeaver earlier, but, it's tooooo messy in it's UI.

        Thanks..

        • mootoday4 hours ago
          Yeah, I've noticed similar things with my projects. Hard to avoid these days I think.

          Awesome, thanks for being an early adopter!

          I got some great feedback already, so I'll continue building it out.

          Roadmap: - Release binaries for Intel Mac, Linux, Windows - Add / test support for more database engines - Wrap up the LLM integration

          Holidays are coming up, it may be a productive time haha

  • xiaohanyu10 hours ago
    Interesting journey of vibe coding a non-trivial project.

    Any more details about why this project is unmaintainable?

    • mootoday5 hours ago
      I'm sure everyone has their own tolerance for what is and isn't maintainable :). For me, not knowing what code exists, where it is, how it fits together, and stuffing it all in one main file feels like a recipe for trouble down the road. Sure, I could probably tell the LLM to split the main file into modules and ask it to refactor code etc.

      However, from personal experience I'm a lot more efficient when I use LLMs to help with tedious, boilerplate-like code writing but I remain in control over structuring the project so it's maintainable by more than machines only.

      I use LLMs every day to write tests for example, it's a massive time saving and I wouldn't want to write tests manually ever again.