AI Weekly Malaysia

Back to items Summaries

Rust changed me as a developer

ID
47401
Status
summarized
Published
17 Nov 2026, 4:16 AM
Fetched
17 Nov 2026, 11:40 PM
Provider
Hacker News
Category
dev-community
Original URL
https://blog.startifact.com/posts/how-rust-changed-me/
Source URL
https://hnrss.org/best

Summary

Score
6.0
Created
17 Nov 2026, 11:40 PM
Tags
Audience
developersvibe_codersai_ml_learners

What happened

Martijn Faassen, writing after 6+ years with Rust (more than 4 of them professional), argues that a sufficiently different language changes how you think, and for him the concrete shift was internalising sum types: an `enum Person { Human { first_name, last_name }, Cat { name, cuteness } }` where `match` forces you to handle every variant, versus the product-type structs most developers default to. He notes the ideas aren't Rust-exclusive but that Rust's compiler enforcement brought them into focus. The Hacker News thread drew 277 points and 173 comments.

Why it matters

If you currently model 'one of several states' with nullable fields, boolean flags, or a stringly-typed status column, this article gives you a named alternative — the sum type plus exhaustive match — and the 173-comment thread is where the cost side gets argued (verbosity, refactor churn, what happens when you add a variant). Worth deciding before your next schema or state machine, not as a language conversion pitch.

Discussion angle

Ask the room for a real case where exhaustive variant handling caught a bug the compiler would otherwise have missed — and a case where it just added ceremony when a variant was added. That split is the useful takeaway, not 'Rust good'.

Top