Programming

20294 readers

419 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

UlrikHD@programming.dev

Here’s how I use LLMs to help me write code | Simon Willison (simonwillison.net)

submitted 1 week ago by yo_scottie_oh@lemmy.ml to c/programming@programming.dev

16 comments fedilink hide all child comments

I appreciate Simon's balanced take on how LLMs can enhance a project when used responsibly.

I'm curious, though—what are this community's opinions on the use of LLMs in programming?

you are viewing a single comment's thread
view the rest of the comments

[–] kn0wmad1c@programming.dev 3 points 4 days ago* (last edited 4 days ago)

The problem with this article is that he stresses that you need to check the code and step in when needed - yet relying heavily on LLMs will invariably make it impossible for you to tell what's wrong and eventually how to even read the code (since it will produce code using libraries you never experimented with because the LLM can just write the code).

Also "vibe-coding" is stupid af. You take out the human element altogether because you just accept all changes without reading them and then copy/paste errors back in without any context.