Learning-Rust.Github.io: Rust Programming Language Tutorials for Everyone
learning-rust.github.io70 points by dumindunuwan 3 days ago
70 points by dumindunuwan 3 days ago
- 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
Books that come into my mind that might be useful to you:
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).
First time announced 2018: https://news.ycombinator.com/item?id=16594547
Now with Human written new design and lot of rewrites to match Rust 2024
Why 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.
First off, in actually using Zola or Hugo, there really is minimal difference in syntax, and I really have to squint to see whether there is stylistic input from their host languages.
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.
Use right tools! don't be a die hard fan of any language.
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.
Fair.
I guess I'm of the wrong mindset that when trying to teach a language, it helps to do all the things in said language, because then you've got lots of fodder to write about and explain other people's code, pointing at your own use case as examples.
As I said, I'm clearly in the weird minority on this one and should have kept my damn trap shut. We are all free to make our own choices.
I suppose too I was coloured by my hatred of Hugo. :)
If anything, I’m less likely to trust learning materials from someone who refuses to consider other languages, especially if they go so far as to avoid using tooling unless it’s written in a specific language.