3 ms·
You could easily write some posts using this: "Most common errors beginners make in Rust" You're like the world expert on this. "What people often get wrong
by TN1ck 6y ago
You could easily write some posts using this:
"Most common errors beginners make in Rust"
You're like the world expert on this.
"What people often get wrong about Rust"
Maybe there are common conceptual issues you spotted?
I'm not sure, but I would also imagine that you explained some things a few times in a more simple language, this could also be a great thing for a blog post. Instead of pointing them to a doc and explaining something about it, point them to your blog post then.
- niedzielski 6y agoI liked this comment because it felt immediately constructive and a great starting point to think about if nothing else. One of probably many examples of this list-based approach (for a different technical subject) is "50 Android Hacks" by Carlos M. Sessa. Avoiding common errors makes sense but are even more valuable when the warnings are paired with idiomatic alternative patterns. https://www.manning.com/books/50-android-hacks https://www.manning.com/books/50-android-hacks