I really like Amos’ style of writting. This is an introduction to Rust, but instead of using the classical “teacher” tone of voice, this blog post follow the thought process of someone trying to rewrite something in Rust while discovering the language. I hope you would enjoy it too!
I found the article really interesting, but I’m not sure that argdown is the solution. Argdown seems really nice to stucture summary comment, but not the discussion itself. I think it’s an excellant starting point which should be explored deeper.
It’s an amazing serie. I can’t wait the next one!
I think that the issue is OOP itself. Having 1-3 lines in a functionnal language (or anything that can use functional idioms) is both idiomatic, more readable and maitainable.
When I read clean code (about 2 years ago), I read it with the point of view of a C++ programmer. I read the advices and skept the code (since java didn’t interest me that much) and I filtered the advices that I though didn’t applied to C++. For this very reason, I found the book relatively good (since I focused only on the good part).
I found this article absolutely on point. I also finally understand why I really don’t like uncle bob’s conferences since I don’t skim or filter them partially but watch the whole content.
Nonetheless, I don’t regret that I read clean code, mostly because it forced me to articulate my thoughts on what I liked/disliked about it. I wouldn’t recommend it though.
Great read. That’s aneamazing and well written story.
It’s not possible because dihydrogen molecul are much thiner than methane or similar gas. This means that conventionnal gas infrastructure will leak dihydrogen.