HackerTube.runGood videos, with context.
Elm Europe 2017 - Evan Czaplicki - The life of a file
About this video
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 it appears in the archive
Recommended as the argument for code colocation and delaying abstraction.
AI-generated summary and labels from the source dataset; verify important details against the video. Source & credits.
From the Hacker News discussion
Just stick everything in the same file until it actually hurts. This presentation[0] gets it right. [0]: [VIDEO]
Read original comment ↗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): [VIDEO]
Read original comment ↗Premature extraction can solidify premature abstractions and create pressure against reabstraction. The creator of Elm has a talk that mentions this: [VIDEO]
Read original comment ↗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) [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.
Read original comment ↗