72K views · Aug 24, 2017 · 47:02 · 4 HN recommenders · 4 mentions · discussed 2019–2025
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.
Why Hacker News points people here: Recommended as the argument for code colocation and delaying abstraction.
“Just stick everything in the same file until it actually hurts. This presentation[0] gets it right.”HN comment, 2022
“Just stick everything in the same file until it actually hurts. This presentation[0] gets it right.”
Argues for keeping everything in one file until it hurts.
Just stick everything in the same file until it actually hurts. This presentation[0] gets it right. [0]: this video
“this great talk by Evan Czaplicki (Elm creator)”
Great talk by Elm's creator on structuring codebases.
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
“The creator of Elm has a talk that mentions this”
Elm creator talks about premature extraction and abstractions.
Premature extraction can solidify premature abstractions and create pressure against reabstraction. The creator of Elm has a talk that mentions this: this video
“Here is one about how to structure a project (roughly)”
Talk on how to structure a project functionally.
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.
