34
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 09 Jul 2026
34 points (88.6% liked)
Programming
27651 readers
283 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 !webdev@programming.dev
founded 3 years ago
MODERATORS
It definitely is capable of it now, if you put some effort into guiding it, and you're working in a popular domain/language. It couldn't really do it a year ago though so you might just be a bit out of date.
I experiment with it quite a bit just because that's what all the employers want right now, and I never get good results. It's not good at making "decisions," and you don't really know what decisions that will need to be made until you start coding. Or, you can meticulously plan and review everything, which can take longer than just writing the code (we already have pretty good precise languages to specify behavior). To be clear, I'm talking about all the small decisions like, "I've already wrote similar code to this, maybe I should refactor it out to a function," "maybe I should use a hashset here instead of an list," "I should probably use stable_sort here instead of sort," "maybe this endpoint should accept PUT instead of POST," etc.