Elm Europe 2017 - Evan Czaplicki - The life of a file
Elm Europe4 HN recommenders · recommended in 4 months, 2019–2025
talk · intermediate · evergreen · 2019–2025 on HN
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.
Up next
5 mo on HNJordan Peterson debate on the gender pay gap, campus protests and postmodernism
Channel 4 News
5 HN recommender · 2018–2023
2 mo on HNElm Europe 2017 - Richard Feldman - Scaling Elm Apps
Elm Europe
2 HN recommender · 2019–2022
2 mo on HNDebunking Dr. Robert Lustig's Claims from The Huberman Lab Podcast | Educational Video | Biolayne
Dr. Layne Norton
2 HN recommender · 2024–2025
12 mo on HNDominion (2018) - full documentary [Official]
Farm Transparency Project
10 HN recommender · 2019–2024
5 mo on HNCaptain Disillusion: World's Greatest Blenderer - Live at the Blender Conference 2018
Captain Disillusion
4 HN recommender · 2019–2022
15 mo on HNRailsConf 2014 - All the Little Things by Sandi Metz
Confreaks
15 HN recommender · 2015–2025
14 mo on HN"Simple Made Easy" - Rich Hickey (2011)
Strange Loop Conference
14 HN recommender · 2022–2026
13 mo on HN"Making Impossible States Impossible" by Richard Feldman
elm-conf
9 HN recommender · 2017–2026
12 mo on HNHow To Design A Good API and Why it Matters
Google TechTalks
12 HN recommender · 2011–2025
11 mo on HNThe Value of Values with Rich Hickey
InfoQ
10 HN recommender · 2014–2023
10 mo on HNOverwatch Gameplay Architecture and Netcode
GDC Festival of Gaming
16 HN recommender · 2019–2025
11 mo on HNSolving Problems the Clojure Way - Rafal Dittwald
Clojure/north
10 HN recommender · 2019–2025
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