this post was submitted on 20 May 2025
407 points (97.9% liked)

Programming

20294 readers
321 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

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 [email protected]



founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 11 points 2 days ago (2 children)

But the real savings? Repetitive code. I suck at it, I always make typos and it’s draining.

It's hard to say without being immersed in the codebase you work on, but wouldn't making your code DRY (when possible) take care of a lot of the repetition without needing to write a bunch of incredibly similar code (be it by hand or with an LLM)?

[–] [email protected] 4 points 2 days ago

I haven't used a LLM to help code in a while (yes I've tried), but I found them useful for repetitive configs, like asset files. Also sometimes it makes sense to just have 5 slightly different lines of code in a row instead of a new function.

In general though, reasonable use of DRY is a good idea. There will still be repetitive parts though where a LLM autocompleter lets you just hit tab 5 times.

[–] [email protected] 0 points 2 days ago

No, it's all different - like a normal use case is "write me a stored procedure to optionally update all fields on a row on this table" or "given the following json response, build a class to parse it into"

We have a ridiculous database and multiple new api's to integrate with every year, so this comes up a lot