Top all-time · #10475
Jeroen Engels
Personal blog · jfmengels.netprogramming
Jeroen Engels writes jfmengels' blog, a personal blog at jfmengels.net about programming. Since 2020, 7 different Hacker News readers have linked it 27 times, most often “Essential and Accidental Configuration”. It is still writing: the last post was on 2026-08-26, and you can follow it by feed.
Too few sampled comments (1) to say how often HN recommends it.?
Why HN links it
HN readers link Jeroen Engels' blog on elm-review and static analysis. The one comment cites his post on safe dead code removal, noting elm-review is good at detecting dead code.
Summarised by Claude from a sample of 1 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Articles by Jeroen Engels, mostly around Elm, static analysis and more generally programming
Most-linked posts?
- Essential and Accidental Configuration2 people · 2 mentions · first linked 2025-07-10
- Safe dead code removal in a pure functional language2 people · 2 mentions · first linked 2021-01-28
- Optimizing for JavaScript Is Hard2 people · 2 mentions · first linked 2022-08-15
- Compiler Reminders2 people · 2 mentions · first linked 2025-04-26
- A Nice Round Ball2 people · 2 mentions · first linked 2023-01-28
What Hacker News says?
Just to clarify: Since elm-review is a static analysis tool separate from the compiler, you can run and compile your program just fine without having to handle all the dead code warnings (which elm-review is actually very good at detecting https://jfmengels.net/safe-dead-code-removal/ ). I myself personally tend to run elm-review when I'm ready to make a PR most of the times.
Comment linking /safe-dead-code-removal/
on “Disable comments make static analysis tools worse”Submitted Safe dead code removal in a pure functional language as a story · 84 points
HN discussionSubmitted Tail recursion, but modulo cons as a story · 76 points
HN discussionSubmitted Disable comments make static analysis tools worse as a story · 60 points
HN discussionSubmitted Compiler Reminders as a story · 38 points
HN discussionSubmitted Constraints and Guarantees as a story · 16 points
HN discussionSubmitted Single out elements using phantom types as a story · 6 points
HN discussionSubmitted Compiler Reminders as a story · 4 points
HN discussionSubmitted What if ESLint's configuration worked like elm-review? as a story · 4 points
HN discussionSubmitted Measuring cognitive complexity with elm-review as a story · 3 points
HN discussionSubmitted Problem with Concurrent Linter Fixes as a story · 2 points
HN discussionSubmitted Essential and Accidental Configuration as a story · 2 points
HN discussionSubmitted Essential and Accidental Configuration as a story · 2 points
HN discussionSubmitted A Nice Round Ball as a story · 2 points
HN discussionSubmitted Multi-files fixes in elm-review as a story · 2 points
HN discussionSubmitted Gaining insight into your codebase with elm-review as a story · 2 points
HN discussionSubmitted Optimizing for JavaScript Is Hard as a story · 2 points
HN discussionSubmitted Optimizing for JavaScript Is Hard as a story · 2 points
HN discussionSubmitted Fixing vulnerabilities in Elm's virtual DOM as a story · 2 points
HN discussionSubmitted Safe dead code removal in a pure functional language as a story · 2 points
HN discussionSubmitted Safe Unsafe Operations in Elm as a story · 2 points
HN discussionSubmitted The caching behind Elm's Html.Lazy as a story · 1 points
HN discussionSubmitted Elm Camp 2024 as a story · 1 points
HN discussionSubmitted A tale of failing to design rule boundaries – Data-last functions as a story · 1 points
HN discussionSubmitted The Omniscient Linter as a story · 1 points
HN discussionSubmitted Implementing multi-file analysis for linters as a story · 1 points
HN discussionSubmitted A Nice Round Ball as a story · 1 points
HN discussion