
Elm Europe
4 HN recommenders · recommended in 4 months, 2019–2025
47:02 · 72K views · Aug 24, 2017
Elm creator Evan Czaplicki's talk on how a file grows and when to split code up. He argues for keeping code in one file until it hurts and warns against premature extraction.
Recommended as the argument for code colocation and delaying abstraction.
4 comments from Hacker News
Great read, as always! The combination of the Elm reference and "coarsely structure codebases around CPU timelines and dataflow" statement reminded me of this great talk by Evan Czaplicki (Elm creator): this video
Just stick everything in the same file until it actually hurts. This presentation[0] gets it right. [0]: this video
There are a lot of lectures/speeches by the creator of elm and Richard Feldman that talk about how to think "functionally" Here is one about how to structure a project (roughly) this video I also think looking at the source code for elm and its website, as well as the elm real world example help a lot.
Premature extraction can solidify premature abstractions and create pressure against reabstraction. The creator of Elm has a talk that mentions this: this video