this post was submitted on 12 Dec 2025
177 points (99.4% liked)
Asklemmy
51663 readers
436 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Fortunately not that bad but the people who are using it do get praised while being a massive burden on everyone who has to review the code or worse, documents.
I did see one clever usage to basically replace most front end devs with AI:
All runs with just
mistral:8b. Very flexible solution compared to having front end devs constantly iterate on a UI monstrosity meant to serve every single clients needs. Of course this assumes the AI is writing the query correctly.So the LLM can run arbitrary code against your database? Or your clients can? Both sound scary as hell!
You're being silly. Clients can only prompt the AI and the AI has restricted read-only permissions on the database. Slap on a execution timeout to cover if the AI wrote an expensive query.
The real concern is the AI getting a query subtly wrong and giving the client bad info. That gets "covered" by some flimsy disclaimer.