Rust's borrow checker gets a reputation for being difficult. That framing is wrong. The borrow checker is a static analysis tool that forces explicit decisions about ownership and lifetime. Things every program has, but most languages let you ignore until runtime. The errors it produces are not bugs: they are descriptions of ambiguous ownership you would have debugged at 2am in a production incident in any other language.
The pattern that makes it click: treat the borrow checker as a pair programmer who cannot be wrong. When it rejects code, it is not saying "your idea is impossible". It is saying "the ownership intent here is unclear, state it explicitly". Nine times out of ten, clarifying ownership reveals a real design question you had been deferring.
In the k3s-dashboard backend, the compiler forced the decision about who owns the Kubernetes client: the request handler, or the application state. The answer is application state wrapped in Arc for shared concurrent access. Without the borrow checker, that decision gets made implicitly, differently by different engineers, and surfaces as a race condition under load.