Hacker News Reader

I've been programming in Rust for the last few years. My daily work is mostly just fumbling through compiler errors until the code works.

Some observations:

- The compiler is always right.

- Do what clippy and rust-analyzer says. Don't ask questions.

- If you're fighting the compiler, clippy, AND rust-analyzer, then you're almost definitely wrong.

Virgins try to use &str everywhere. Chads just use String.

View on HN

This sounds like a terrible way to exist.

Happy way to exist!

I suppose ignorance is bliss after all - I mainly hope you are exaggerating when you say 'fumbling through'.

Getting paid to mechanically crank through compiler errors? Sounds okay actually!

I wonder what approach acts as the best mentor for someone who wants to eventually develop a good mental model for how systems work. The C approach where you suffer at runtime and then have to debug ferociously, or the Rust approach where your mentor hits you with a stick all day?

I had C programming experience before touching Rust. I may be biased, but I think this is the right way to understand how computer systems work. Otherwise, Rust's design choices will make little sense to you.

Reply on news.ycombinator.com