I'll give it a read! I wouldn't have expected much relevant info on the Arch Wiki.

I'm not autistic but I like most of these things.

Not a trustworthy news source. They haven't vetted any of this information, they're literally just reposting tweets that have since been shown to be fake. For example: https://x.com/RightWingCope/status/1992436934032208008

I have the same urge, but rather to be a teacher/mentor than a parent. Too bad the US doesn't want to pay teachers what they're worth, or I'd strongly consider a career change.

I heard that motherfucker had like... 30 god-damned dicks.

The only correct answer is to be consistent with the code base you're working in or the language's conventions. If neither of these conventions exist, then someone has already failed you.

Let's not lower the standard anywhere near Trump.

Sounds like Kubuntu's fault to me. If they provide the desktop environment, shouldn't they be the ones making it play nice with the Linux scheduler? Linux is configurable enough to support real-time scheduling.

FWIW I run NixOS and I've never experienced lag while compiling Rust code.

"how to write sloppy rust code and squander most of the advantages of the language"

Only half serious. But I think really the only point that I agree with is taking the easy way out with the borrow checker. I mean, at least try to borrow when it's idiomatic, but if you get frustrated, clone (or move) instead.

Error handling when done well is not much harder than unwrapping everything, and you get many advantages. Learn to use thiserror for your library crates and anyhow for executables.

I also agree that you should avoid unsafe 99% of the time. If you think you need it, you probably don't.

Nah these are the actual integer representations. Otherwise you would have Some(None) == Some(Some(None)) which is way too Javascripty for Rust folks.

Do challenging projects. Read code from better engineers. Work with better engineers. Try new languages that actually solve technical problems instead of just having nice syntax. Contribute to open source projects that you use. Actually read the manuals that come with your tools. Notice when it's taking you a long time to do something and reflect on it to find a faster way. Constantly tweak your workflow to be more productive.

And the most important of all:

Get a split ergomech keyboard.

Don't forget about lsd