1531
Many will be triggered
(sh.itjust.works)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 22 Oct 2024
1531 points (96.5% liked)
memes
10696 readers
2720 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads
No advertisements or spam. This is an instance rule and the only way to live.
Sister communities
- !tenforward@lemmy.world : Star Trek memes, chat and shitposts
- !lemmyshitpost@lemmy.world : Lemmy Shitposts, anything and everything goes.
- !linuxmemes@lemmy.world : Linux themed memes
- !comicstrips@lemmy.world : for those who love comic stories.
founded 2 years ago
MODERATORS
I have nightmares where the borrow checker is shouting at me incomprehensibly about the literal bugs and I shoot them with the clone laser and the borrow checker stops shouting for ten seconds, but now there are two bugs for each original bug and Tim Berners Lee floats by saying it's not very idiomatic and I shouldn't expect to get to work on time if I just keep stopping along the journey to spend all my time cloning the bugs.
Haha. On a more serious note, it gets better over time. I recommend keeping a really functional programming style in Rust and only opt out to imperative programming, when it just makes sense (e.g. to optimize, avoid allocs etc.). I'd say Rust is currently my most productive programming language, because I mostly avoid the time-consuming debugging part due to the strictness.
Thanks for the encouragement, kind fellow former redditor.