Twitter at the speed of parenting
If you have to add a conditional in your reused code, you shouldn’t be reusing itpic.twitter.com/dTNWErJf6K
Show this thread
100% agree. As I’ve said before - many people think DRY (“don’t repeat yourself”) means syntax or structure, when it really means concepts.https://twitter.com/rtfeldman/status/1092885754265489408 …
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
*nodnod* still trying to figure out the best way to talk about this for teaching. Best I’ve got so far is talking about “writing code so that you minimize the number of things you have to remember to change (or not change) when you alter functionality in the future”
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I think the problem is we often shoot for reuse too early. Many moons ago, they taught us about the ‘Evolving Frameworks Pattern Language’, I only remember that they said (paraphrasing) “Don’t reuse until you have 3 examples”.
-
My thesis around this is that any system has its own internal logic, or "pattern", which is not explicit nor apparent, but rather emergent. It emerges as you write the program, but is not necessarily your personal architectural choice.
-
I think that is largely the premise of the “Evolving Frameworks” paper.
-
Interesting! Haven't read but it seems that I should. Thanks for the info!
New conversation -
-
-
Code duplicating is just an indicator to *possible* concept duplication you can extract
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I first heard this called "information hiding" (Parnas).
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Software is soft until it's DRYed
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.