Post #4659704 · Elektrine

2026-09-01 15:55 UTC

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.

Replies (1)

@MangoCats@feddit.it 2026-09-01 20:03

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.

Open ##4659703