this post was submitted on 10 Apr 2025
529 points (96.5% liked)

Technology

69109 readers
3131 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
L4s@hackingne.ws
529
Facebook Pushes Its Llama 4 AI Model to the Right, Wants to Present “Both Sides” (www.404media.co)
submitted 1 week ago by cm0002@lemmy.world to c/technology@lemmy.world
137 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] dermanus@lemmy.ca 6 points 1 week ago (2 children)

I'm in software and we're experimenting with using it for certain kinds of development work, especially simpler things like fixing identified vulnerabilities.

We also have a pilot started to see if one can explain and document an old code base no one knows anymore.

[–] cmhe@lemmy.world 4 points 1 week ago* (last edited 1 week ago) (1 children)

Good code documentation describes why something is done, and no just what or how.

To answer why you have to understand the context, and often, you have to be there when the code was written and went through the various iterations.

LLMs might be able to explain what is done, with some margin of error, but why something is done, I would be very surprised.

[–] dermanus@lemmy.ca 4 points 1 week ago

you have to be there when the code was written and went through the various iterations.

Well, we don't have that. We're mostly dealing with other people's mistakes and tech debt. We have messy things like nested stored procedures.

If all we get is some high level documentation of how components interact I'm happy. From there we can start splitting off the useful chunks for human review.

[–] buddascrayon@lemmy.world 2 points 1 week ago (1 children)

I can honestly see a use case for this. But without backing it up with some form of technical understanding, I think you're just asking for trouble.

[–] dermanus@lemmy.ca 1 points 1 week ago

100%, we're doing human and automated reviews on the code changes, and the code explanation is just the first step of several.