[-] exgf@programming.dev 1 points 1 week ago

Oof, thank you for the catch.

[-] exgf@programming.dev 2 points 1 week ago

I am in total agreement EXCEPT where I differ is that I believe no autogenerated docs should be committed to the repo without being proofread and improved. I see it like scaffolding.

[-] exgf@programming.dev 0 points 1 week ago

It's only effective if the person has actual done something.

[-] exgf@programming.dev 0 points 1 week ago

Every project is way too heavy on the dependency side imo, removing as many deps as I can from my projects is on the TODO list.

[-] exgf@programming.dev -3 points 1 week ago* (last edited 1 week ago)

Well aren't you a bright little ray of light. At this moment your question is akin to saying "You can't write all the scaffolding instead of running cargo new --bin oh_wow_im_so_leet_i_disparage_my_brothers_and_sisters_sharing_open_source_software_for_free"

Go skim through my Github if you want to call me a "developer", pick a project and contribute.

Who in their right mind would sit around writing insane regex for weeks, of course this particular project was augmented with a conversation with an LLM.

Nice undocumented fork of project though. Proud of u.

[-] exgf@programming.dev 1 points 1 week ago

๐Ÿ˜‚๐Ÿ˜‚๐Ÿ˜ญ

-3

cross-posted from: https://programming.dev/post/38477847

Awful Rustdocs is a CLI tool that generates or improves Rustdoc comments by harvesting symbols via rust_ast.nu, enriching each item with ast-grep context (callers, intra-body calls, qualified paths), and prompting your LLM to produce concise, high-quality docs.

You don't need hundreds of prompts and agents if you're smart about your context.

I'm running it on all my Rust projects right now using the Systems Programming Qwen 3 4B finetune I created, and it saves me an incredible amount of time by creating docs that are almost always good enough to publish straight off but act more as a draft for me. It cuts down on a lot of repetitive typing and lets me get back to doing what I love (writing code).

It requires Nushell, but you should probably already be using that, and if this is how you find out about Nushell, then even better, make the jump; it's worth it.

6

cross-posted from: https://programming.dev/post/38477847

Awful Rustdocs is a CLI tool that generates or improves Rustdoc comments by harvesting symbols via rust_ast.nu, enriching each item with ast-grep context (callers, intra-body calls, qualified paths), and prompting your LLM to produce concise, high-quality docs.

You don't need hundreds of prompts and agents if you're smart about your context.

I'm running it on all my Rust projects right now using the Systems Programming Qwen 3 4B finetune I created, and it saves me an incredible amount of time by creating docs that are almost always good enough to publish straight off but act more as a draft for me. It cuts down on a lot of repetitive typing and lets me get back to doing what I love (writing code).

It requires Nushell, but you should probably already be using that, and if this is how you find out about Nushell, then even better, make the jump; it's worth it.

-3

Awful Rustdocs is a CLI tool that generates or improves Rustdoc comments by harvesting symbols via rust_ast.nu, enriching each item with ast-grep context (callers, intra-body calls, qualified paths), and prompting your LLM to produce concise, high-quality docs.

You don't need hundreds of prompts and agents if you're smart about your context.

I'm running it on all my Rust projects right now using the Systems Programming Qwen 3 4B finetune I created, and it saves me an incredible amount of time by creating docs that are almost always good enough to publish straight off but act more as a draft for me. It cuts down on a lot of repetitive typing and lets me get back to doing what I love (writing code).

It requires Nushell, but you should probably already be using that, and if this is how you find out about Nushell, then even better, make the jump; it's worth it.

exgf

joined 1 week ago