28

I just read how someone on RetroArch tries to improve documentation by using Copilot. But not in the sense as we might think. His approach is to let Copilot read the documentation and give him follow-up question a hypothetical developer might have. This also could be extended to normal code I guess, to pretend it being a student maybe and have it ask questions instead generating or making changes? I really like this approach.

For context, I myself don't use online Ai tools, only offline "weak" Ai run on my hardware. And I mostly don't use it to generate code, but more like asking questions in the chatbox or revising code parts and then analyze and test the "improved" version. Otherwise I do not use it much in any other form. It's mainly to experiment.

you are viewing a single comment's thread
view the rest of the comments
[-] thingsiplay@lemmy.ml 3 points 1 day ago

Ah I see, thanks for the link. I don't think the case I talked about is the same case as Rubber duck debugging. It's not to read aloud (maybe in front of another programmer or audience). It's more like, if your students or end user read the documentation and still have some questions left at the end. And ask you the questions about stuff they did not understand.

this post was submitted on 26 Feb 2026
28 points (81.8% liked)

Programming

25793 readers
359 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 2 years ago
MODERATORS