Learning Rust For No Good Reason

April 11, 2026 · 337 words · 2 min read

Sometimes interesting is enough.

I find myself circling Rust while having almost no practical need for it.

These days most of the code I write is just API glue, tiny scripts, small TUIs and random side projects that feel useful for about three evenings, eventually ending up archived. None of this needs borrow checking or fearless concurrency, so JavaScript or Go would do. In most cases even Bash would do.

Rust ended up clicking in a way I did not expect. Annoyingly, almost. And the compiler is strict, but the strictness feels helpful, not punishing, and I find that it makes me slow down, name the thing properly, understand who owns what, and stop overthinking the shape of the app. That part is really new for me, because I am very comfortable living in glue code, where the job is mostly to move data from one shape into another and keep the edge cases from breaking the app. That's all fun, but doesn't really feel like I am learning the material underneath. What Rust does there is to pull me one level lower, in the sense that I have to be careful about memory, errors, lifetimes, and all the tiny decisions I normally let the runtime worry about.

I also like that it makes tiny programs feel substantial. A throwaway CLI in Rust has weight to it, because there is a project structure, a proper compiler, helpful errors, and a real sense that the thing could grow, if I wanted it to. In most cases it probably will not! Most of my little tools sit there like the rest of the stuff I work on, half useful and mostly forgotten.

And maybe that is why I keep coming back. I do not have a grand plan to become a Rust person and I am not rewriting any of my current stuff in it. I'm too busy to pretend every problem needs a systems language. I just enjoy being made to think a bit harder than usual.

That's probably the whole appeal.