4 ms·
A few years ago I bought the book written by the same author. A few chapters in, and I now filter out anything written by Kerkour. This time I missed who the a
by koiueo 2y ago
A few years ago I bought the book written by the same author. A few chapters in, and I now filter out anything written by Kerkour.
This time I missed who the author is and started reading. A few paragraphs in, and I’m scrolling to the bottom to see, who the author is — yep, they did it again.
I have a suspicion, the author might be a recent graduate with only Rust in their belt and not much experience in the industry, trying to quickly climb the career ladder pretending they are something else.
- IshKebab 2y agoDid what again? This seems like solid advice to me. What specifically do you disagree with?
- koiueo 2y agoWell, the advice to not use lib and mod is a sound one. I realized that too. Workspaces – definitely, although, that's borderline useful, because it's hard for me to imagine someone growing their Rust codebase without knowing about this feature. Other tips continue the downward trend. It's hard to disagree with these tips, because they argue for general good (although devcontainer is a controversial one, imo). But anyone with minimal hands-on experience likely already knows all of that. Honestly, reading this article the second time I think my initial comment might've been too harsh. Maybe I've been salty after remembering that book by the author I didn't like But I still stand by my words, that the article turned out somewhat superficial and not insightful.