Programming

27926 readers

112 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 3 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

UlrikHD@programming.dev

bugsmith@programming.dev

Spyro@programming.dev

AI Software Development Is Near-Impossible (www.youtube.com)

submitted 1 month ago by abbadon420@sh.itjust.works to c/programming@programming.dev

80 comments fedilink hide all child comments

Support this channel on Patreon ► https://www.patreon.com/zoranhorvatGenerative AI can write code, but it cannot develop software on its own. Here is why the...

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

[–] toofpic@lemmy.world 1 points 1 month ago (1 children)

Fable was "just ask and get it done" quality level, but really I don't get THAT much bugs - about the same amount that I see irl developers do: get a new feature, find 5 problems, get them fixed, find one more, done. As a recommendation - try to alleviate the biggest problems that ai models have:

overconfidence - skipping wrong stuff "because they have a note saved that it works" or losing the point where they stopped after a session broke, then making things up. Test Driven Development solves the majority of problems like that - when Claude writes tests first, then it's not able to bullshit me that the job is done when "everything is red"
even with large contexts, they run out and stuff gets lost. So if you're not doing something really compact, make your ai document everything, document the feature they are working on now, make it then offload it to permanent doc when that piece is finished. When the ai will fuck up next time, you can tell it to "go read some docs" and most of the times it will work

[–] hperrin@lemmy.ca 3 points 1 month ago* (last edited 1 month ago)

I’m glad it works for you, but it simply does not work for me. Maybe you could try yourself on some of my libraries, because I have never gotten it to save me any time. It’s just spending money and making the work less fun for no reason. Oh, also not having the copyrights to the things that go in my code base, don’t forget that.