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.
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.
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.
Awesome... for databases containing large number of tables, you can pre-process the tables and generate embeddings for each. Then, when user asks a question in plain english, filter relevant tables using in-built vector search and pass metedata of these only as context to LLM.
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.
Author wanted to try vibe coding, despite being a critic. Says that result is unmaintainable.