Programming

28481 readers

229 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

123

Void Linux maintainer orphans 100+ packages over AI policy dispute (www.phoronix.com)

submitted 4 days ago by HaraldvonBlauzahn@feddit.org to c/programming@programming.dev

33 comments fedilink hide all child comments

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

[–] chloroken@lemmy.ml 9 points 4 days ago (2 children)

Trust me, nobody trusts you.

[–] douglasg14b@lemmy.world 4 points 2 days ago* (last edited 2 days ago)

That's a great way to alienate people who are trying to start discussions. Good job.

Do you have the expertise and experience to state what is or isn't important for PR change review? The data to back up defect rates and outages?

If not, then you're just speaking out of your ass and with your emotions instead of with logic.

[–] NotSteve_@lemmy.ca 0 points 4 days ago* (last edited 4 days ago) (3 children)

Do you work in tech? How often do you submit PRs? AI reviews are one of the best applications for the technology and non-LLM CI tools have existed for ages to serve a similar but less efficient purpose

I don't like what AI has done to the software industry but we need to give credit where its due

[–] HaraldvonBlauzahn@feddit.org 14 points 3 days ago (1 children)

Do you work in tech?

One canwork in tech and not use LLMs. Your comment sounds like it should be the norm, or already is.

Also, the discussion is about using LLMs in open source projects, which put a lot more focus on understandable and maintainable code than the software industry typically happens to do.

[–] black0ut@pawb.social 4 points 3 days ago (1 children)

I work in tech and I don't use LLMs. From my experience, they're catastrophic especially in those positions where they review code/actions. Reviews are the last line of defense against bad code, bugs, vulnerabilities or destructive actions. Giving that role to an RNG parrot that is often confidently wrong is almost suicidal.

[–] HaraldvonBlauzahn@feddit.org 2 points 3 days ago* (last edited 3 days ago)

From my experience, they’re catastrophic especially in those positions where they review code/actions.

That's interesting. I am currently searching for ways that I can use them a bit to chill-pill our CTO without sinking the company (which is very deep in the water with technical debt).... at least until I get another job.

Can you expand why they are that bad in this use?

My current idea is to pin up new architecture by hand, define new interfaces by hand, and then let the LLM occasionally fill in a function body. And maybe, maybe, an "ai refactored" branch which has just the purpose to showcase what happens if one is not careful - and will never be merged, at least not by me.