Rust changed me as a developer

271 points · 172 comments on HN · read original →

Points and comments are a snapshot, not live.

Rust's sum types, ownership system, and macros improved the author's programming architecture and thinking.

The author, a 6-year Rust user (4+ years professional), describes how Rust changed their development approach. Key insights include sum types (enums) as superior to interfaces for fixed variants, type-driven development as a design tool alongside testing and documentation, compile-time macros enabling patterns like serde serialization and clap CLI parsing that mimic runtime magic, and ownership/borrowing forcing cleaner, less coupled code architecture. The arena pattern (storing nodes in an array indexed by integer IDs) solves circular references that Rust's ownership model forbids.

What commenters are saying

Commenters broadly agree that exposure to significantly different languages is valuable, not just Rust. Multiple commenters share personal examples: learning Sudoku generation in Odin, Elixir and the BEAM, hardware description languages like Verilog for physical parallelism. One commenter notes these features exist in older languages like Standard ML. A controversial comment recounts a personal struggle with a Sudoku solver assignment that contributed to later career difficulties. The thread emphasizes that different paradigms teach transferable lessons, though 'major project' is subjective.