[al_be_back]

>> My friends and I were complaining about having to decipher incomprehensible code one day

Your raw sample files [1] are already highly descriptive: filenames, component names, variables etc etc. the auto-generated comments add only noise (increase file size). I would use complex, hard-to-decipher incomprehensible code to show how these comments bring sense forth. Perhaps let it loose on the Linux Kernel source, see what it does - an idea

Personally, I prefer the doc-as-you-code approach, especially using context-aware naming. When code's cryptic & large, i try to visualise it e.g. Sequence Diagram from code (intellij).

[1] https://swiftstart.notion.site/Sample-files-acfb097bbf214210...

[swiftstart]

Thanks for the feedback! That's a really good idea and we will definitely give that a shot!

If it provides more clarity, we are trying to tackle this in stages. Can the AI produce helpful and descriptive code for 1. Basic + Short (less than 100 lines) files? 2. Basic + Long (more than 100 lines) files? 3. Complex / Vague + Long files?

After stage 3, which I believe is what you are referring to, we then hope to explore stage 4. 4. Can AI incorporate programmers' intentions into the comments?

[davidguetta]

100% I've had this problem in the past and the functinos were way more obscure than something called " get_doc_from_code ".

Can it even deobfscuate code ?