Elm Europe 2017 - Evan Czaplicki - The life of a file on HackerTube: recommended by 4 Hacker News commenters across 4 separate months, 2019–2025.
talk · intermediate · evergreen
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.
“Just stick everything in the same file until it actually hurts. This presentation[0] gets it right.”
4 Hacker News comments link this video. Each one links back to its thread.
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
in “Clean your codebase with basic information theory” · View on HN
Just stick everything in the same file until it actually hurts. This presentation[0] gets it right. [0]: ▶ this video
in “Code colocation is king” · View on HN
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.
in “Thoughts on Go vs. Rust vs. Zig” · View on HN
Premature extraction can solidify premature abstractions and create pressure against reabstraction. The creator of Elm has a talk that mentions this: ▶ this video
in “38% of bugs at Airbnb could have been prevented by using types” · View on HN