Learning-Rust.Github.io: Rust Programming Language Tutorials for Everyone
learning-rust.github.io
Learning-Rust.Github.io: Rust Programming Language Tutorials for Everyone
1–10 of 12 posts
Re: Learning-Rust.Github.io: Rust Programming Language Tutorials for Everyone
#2Now with Human written new design and lot of rewrites to match Rust 2024
Re: Learning-Rust.Github.io: Rust Programming Language Tutorials for Everyone
#3At least use Zola instead of Hugo…
I know I’m in the my, but I believe in using the language fully if you’re going to provide a learning resource for said langauge.
Re: Learning-Rust.Github.io: Rust Programming Language Tutorials for Everyone
#4- how to break a problem into constituents
- how to model or architecture a solution before writing code for it
- how to decide which approach would be reasonable if there are multiple ways to model the aforesaid problem
Re: Learning-Rust.Github.io: Rust Programming Language Tutorials for Everyone
#5Why not some Rust in your website stack? At least use Zola instead of Hugo… I know I’m in the my, but I believe in using the language fully if you’re going to provide a learning resource for said langauge.
Re: Learning-Rust.Github.io: Rust Programming Language Tutorials for Everyone
#6Why not some Rust in your website stack? At least use Zola instead of Hugo… I know I’m in the my, but I believe in using the language fully if you’re going to provide a learning resource for said langauge.
Second, people should use the tools they want to to get the job done. If they already know Hugo, and they want to create a blog, it's fine that they use Hugo.
Finally, the bigger decision that the blogger seems to be trying to make is to avoid LLMs in writing, which I admire, and IMO is the far more important technology choice in making their blog.
Re: Learning-Rust.Github.io: Rust Programming Language Tutorials for Everyone
#7- is there a course or a guide that you on HN are familiar with that goes one step above - how to break a problem into constituents - how to model or architecture a solution before writing code for it - how to decide which approach would be reasonable if there are multiple ways to model the aforesaid problem
A Philosophy of Software Design — John Ousterhout
Designing Data-Intensive Applications — Martin Kleppmann
Domain-Driven Design — Eric Evans
There might be some courses as well, but I never looked into them.
This also works quite well:
Write down the problem. Think real hard. Write down the solution. (Thank you, Feynman).
Re: Learning-Rust.Github.io: Rust Programming Language Tutorials for Everyone
#8Why not some Rust in your website stack? At least use Zola instead of Hugo… I know I’m in the my, but I believe in using the language fully if you’re going to provide a learning resource for said langauge.
However, I used many tech stacks including Hexo navy theme, Docusaurus, Docsy but ended up creating my own setup with Hugo. If you can see, in the project it's more or html/css that can be used with any builder.
Re: Learning-Rust.Github.io: Rust Programming Language Tutorials for Everyone
#9- is there a course or a guide that you on HN are familiar with that goes one step above - how to break a problem into constituents - how to model or architecture a solution before writing code for it - how to decide which approach would be reasonable if there are multiple ways to model the aforesaid problem
Re: Learning-Rust.Github.io: Rust Programming Language Tutorials for Everyone
#10Why not some Rust in your website stack? At least use Zola instead of Hugo… I know I’m in the my, but I believe in using the language fully if you’re going to provide a learning resource for said langauge.