57
Do you actually read documentation, or just search it when you’re stuck?
(programming.dev)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 29 Oct 2025
57 points (98.3% liked)
Programming
25522 readers
283 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
As a great example of the last point I LOVE this thing. https://doc.rust-lang.org/stable/rust-by-example/
Rust has an official book but it also has this list of runnable programs going over the features and usage.
So when I want to quickly see/remember a topic I can just look at it but if I want to learn inner workings in more detail to mess around with I can search it in the other documentation.
Damn, even when I don't mention it, it's apparently obvious that I'm gushing about Rust. 😅
I had the Rust CLI Book in mind: https://rust-cli.github.io/book/index.html
Especially, if you have experience in another language already, the first chapter shows you how to develop and ship a useful Rust application in a short amount of time. And then the second chapter contains all the detail information, which you might need, after you've run off and started building your own thing.
But yes, Rust By Example is also really great. It happens a lot that you search "xyz in Rust" and it's one of the first results, and always worth clicking on.