THE VIDEO SHELF · code organization
Elm Europe 2017 - Evan Czaplicki - The life of a file
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 HN readers recommended it
Recommended as the argument for code colocation and delaying abstraction.
This is a summary from the source dataset, not an endorsement by Hacker News or the video creator.
Video & recommendation details
- Creator / channel
- Elm Europe
- Topic
- code organization
- Format
- talk
- Level
- intermediate
- HN recommenders in dataset
- 4
- HN mentions in dataset
- 4
- Recommendation years in dataset
- 2019–2025
These counts and years describe the included Hacker News records; they are not YouTube views or the video’s publication date.
From the original HN conversations
Excerpts from the recorded comments. Follow each source for the full comment and surrounding discussion.
Just stick everything in the same file until it actually hurts. This presentation[0] gets it right. [0]: [VIDEO]
yakshaving_jgt on Hacker News · 2022-02
In Code colocation is kingGreat 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): [VIDEO]
gabigrin on Hacker News · 2024-02
In Clean your codebase with basic information theoryPremature extraction can solidify premature abstractions and create pressure against reabstraction. The creator of Elm has a talk that mentions this: [VIDEO]
hombre_fatal on Hacker News · 2019-02
In 38% of bugs at Airbnb could have been prevented by using types
Summaries, classifications and recommendation records are from the HackerTube source dataset. Read about this library and its limitations.