Re:Why Reliability Demands Functional Programming
by agumonkey on Sunday December 28, 2025 @11:12AM
(#46412076)
this makes me want to move to a haskell (or any hard fp language) shop in 2026..
[ Parent
| on HN ]
Re:Why Reliability Demands Functional Programming
by kephasp on Sunday December 28, 2025 @05:54PM
(#46415350)
I've been using Haskell professionally for the last 5 years, I definitely hope I can continue!
Re:Why Reliability Demands Functional Programming
by tariqshams on Sunday December 28, 2025 @11:28PM
(#46417474)
Genuinely curious on the types of projects you use Haskell for! I’ve been thinking of learning it beyond the lightweight treatment I got during my CS degree.
Re:Why Reliability Demands Functional Programming
by rastrian on Monday December 29, 2025 @12:43AM
(#46417830)
Mostly “boring” stuff where the type system pays rent fast:
- Domain/state machines (payments/fulfillment-style workflows): modeling states + transitions so “impossible” states literally can’t be represented. - Parsers/DSLs & config tooling: log parsers, small interpreters, schema validation, migration planners. - Internal CLIs / automation: batch jobs, release helpers, data shapers, anything you want to be correct and easy to refactor later. - Small backend services when the domain is gnarly (Servant / Yesod style) rather than huge monoliths.
If you’re learning it beyond CS exposure, I’d start with a CLI + a parser (JSON/CSV/logs), then add property-based tests (QuickCheck). That combo teaches types, purity, effects, and testing in one project without needing to “go full web stack” on day 1.