this post was submitted on 01 Sep 2026
214 points (90.8% liked)

Technology

87708 readers
4338 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] ViceroTempus@lemmy.world 1 points 4 hours ago (1 children)

Yeah I've been using LLM's in Rider for over a decade. I don't have a problem with LLM's. I do have a problem with how they're currently used, and how people keep trying to use them to replace their own thinking.

I think they have a place in the coding scene, a limited niche place, but a place none the less. They just aren't a replacement for software engineers. Architecture and intention are the big differences to me. An LLM cannot understand intention, it just makes statistical guesses that are often wrong.

[โ€“] MangoCats@feddit.it 1 points 12 minutes ago

An LLM cannot understand intention, it just makes statistical guesses that are often wrong.

True, when you give a prompt like: "make me a contact management / constant contact app which I can deploy on AWS and scale to 100,000 users." you get, mostly garbage. If you specify how you want the UX to flow, what fields are most important, what fields should be included in deeper interfaces, what the scheduling looks like, how it gets tuned, what the reports look like, etc. etc. etc. - in other words: give it real requirements and specifications.

Then, pay attention as it develops, you'll ususally find that the requirements you gave it aren't exactly what you really wanted, and when you see what it built that doesn't match with your visions, you can have it revise the requirements and specs.