mootoday
Joined 2 years ago
Karma
87
Submissions
67
Member since
Apr 7
Recent submissions
Comment · 8 months ago
AI of course
Comment · 8 months ago
https://seaquel.app/
It's the SQL client I've always wished I had. It's a desktop app, but I made it work in the browser too thanks to DuckDB Wasm.
Comment · 8 months ago
And now there's a skill to do just that.
Comment · 8 months ago
You don't need a vendor-locked solution for AI agents to work in their own isolated environments :-).
- https://sprites.dev - https://mise.jdx.dev - https://fnox.jdx.dev
Develop a small API that accepts a prompt, starts a sprite sandbox, and then you wait for the AI agent to open a pull request.
I developed that in less than a week and now my client owns the code, can customize it to their needs, and if they want to use a different compute environment, they can with minimal code changes needed.
Comment · 8 months ago
https://seaquel.app
Month 2 of building the SQL client I've always wished I had.
One feature I'm especially proud of is the visual query builder. Drag & drop to build SQL queries.
There's also an entire SQL tutorial section for anyone who wants to learn or refresh SQL knowledge.
Comment · 9 months ago
I built something similar after reading the blog post, based on sprites.dev.
A day of work to get the prototype working and a few hours the next day to allow multiple users to authenticate.
It's surprisingly simple.
Comment · 9 months ago
After reading the article, I built a tool like that with sprites.dev. There's a websocket to communicate stdout and stderr to the client.
Web app submits the prompt, a sandbox starts on sprites.dev and any Claude output in the sandbox gets piped to the web app for display.
Not sure I can open source it as it's something I built for a client, but ask if you have any questions.
Comment · 10 months 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
Comment · 10 months 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.
Comment · 10 months 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.
Comment · 10 months ago
There we go, all set up!
Comment · 10 months ago
It was frictionless to get everything up and running.
Communication between the frontend and backend is via an `invoke` method, easy as pie :).
It's not open source, but once I get the Apple developer stuff all done, I'll add an auto-update feature and open source it.
Comment · 10 months ago
A database desktop client, built with Tauri & SvelteKit.
"But there are many already!" I hear the crowd exclaim.
I respond, "Yes, but..."
It's really something I want for myself. Lightweight, as fast as humanly possible, extensible via plugins (in fact the entire app is mostly plugins, with a small core to glue it together), and a tiny bit of LLM (call it AI if you wish) integration to ask questions about the database or generate/review queries.