Dan Abramov The wet codebase
Channel:eswarnichtsmehrfrei · Length:25:01 · Published:2021-03-14 · Views:26612
Summary
Dan Abramov's talk on the wet codebase, using visualizations to show how removing all duplication too early produces wrong abstractions that are hard to unwind.
Why HN recommends it
Recommended in DRY versus duplication debates for its visuals and its case that copy/paste can beat a wrong abstraction.
Seeing what a premature, wrong abstraction looks like visually was eye opening. — HN, 2024
Software architecture & design · Testing, debugging & developer tools
Subtitles (excerpt)
hi i'm going to drink a lot of water um hi my name is dan abramov i work on a javascript library called react uh this is actually the first conference that i speak at that is not like specific to react to javascript so i'm just curious have any of you ever used react at all okay yeah a lot of people use react that's cool this talk is not about react it's you can say it's a talk about something that i if i had a time machine and could come back to my past self i would tell myself that talk so it's a talk about the code base uh far far away deep under the sea and uh it's a good base that i worked on a long time ago and in the in that code base there were two different modules two files and my colleague and friend was working on a new feature in one of those files and they noticed that actually that feature something very similar was already implemented in another file so they thought well why don't i just copy and paste that code because it's pretty much the same thing and they asked me to review the code and i just read all the books about the best practices pragmatic programmer clean coder well-groomed coder and i knew that i needed to like you're not supposed to copy and paste code because
On Hacker News
The visualizations in Dan Abramov’s talk “The wet codebase” [1] really burned this concept in for me. Seeing what a premature, wrong abstraction looks like visually was eye opening. [1] [VIDEO] — halfcat, 2024-05
Dan Abramov talks about WET (write everything twice) [1] as generally a good approach, primarily because you often don’t know the right abstraction up front, and a wrong abstraction is way worse than a copy/paste. He has some good visuals that illustrate how incorrectly dependent and impossible to unwind wrong abstractions can become. [1] [VIDEO] — halfcat, 2024-08
In my career as a software dev I've found one thing to be true - Every Paradigm I ingest that opens new windows of opportunity are great at first pass and as I learn more the more narrow the scope they can be applied. (This is kinda true in life, too. Like when people say, "Its econ 101 or bio 101." etc. What seems like a statement about 'common' knowledge is actually an indication of how shallow… — shadowfoxx, 2023-08
I like Dan Abramov's "The Wet Codebase" ( [VIDEO] ) -- I've been guilty of doing just what he says in his talk at first, removing all duplications and making the codebase DRY. But then I came to like "prefer duplication over the wrong abstraction", as Sandi Metz puts it. Sometimes it's good to wait to have more data to make an easier and more informed decision. — gosukiwi, 2023-08
I agree with the general sentiment of your comment and I think there are several factors at play here. * The human brain is not capable of evaluating and re-evaluating every possible option amongst the plethora of technical choices developers are faced with. This forces us to develop certain coarse grained mental heuristics (prejudices and biases) to navigate technology, and even if these broad g… — throwitaway1123, 2024-10
Related videos
- Daniel Schmachtenberger on The Portal (with host Eric Weinstein), Ep. #027 - On Avoiding Apocalypses · Eric Weinstein · 3:33:35
- RailsConf 2014 - All the Little Things by Sandi Metz · Confreaks · 38:47
- "Simple Made Easy" - Rich Hickey (2011) · Strange Loop Conference · 1:01:38
- "Making Impossible States Impossible" by Richard Feldman · elm-conf · 25:06
- "Testing Distributed Systems w/ Deterministic Simulation" by Will Wilson · Strange Loop Conference · 40:20
- 🚀 TDD, Where Did It All Go Wrong (Ian Cooper) · DevTernity Conference · 1:03:55
- Bret Victor - Inventing on Principle · Rui Oliveira · 54:20
- How To Design A Good API and Why it Matters · Google TechTalks · 1:00:19
- The Value of Values with Rich Hickey · InfoQ · 31:43
- Overwatch Gameplay Architecture and Netcode · GDC Festival of Gaming · 1:04:03
- Solving Problems the Clojure Way - Rafal Dittwald · Clojure/north · 1:02:26
- Lecture 1A: Overview and Introduction to Lisp · MIT OpenCourseWare · 1:12:55
- Debugging Under Fire: Keep your Head when Systems have Lost their Mind • Bryan Cantrill • GOTO 2017 · GOTO Conferences · 52:34
- "Performance Matters" by Emery Berger · Strange Loop Conference · 42:15
- Alan Kay - Normal Considered Harmful · powerfuloutlet · 1:07:26
- A Philosophy of Software Design | John Ousterhout | Talks at Google · Talks at Google · 1:01:40