I feel this video could've a little more examples in code specifically, but this is by far one of the most enjoyable videos I've seen on coding practices! I love the illustrations, the examples, and how (mostly) DRY the video was! Good job, be proud.
We live in the era of AI assisted code. Readability is more useful than DRY. They are not the same thing. Its honestly just easier to write the code as verbose or as concise as you want it, as long as its easy to understand. This is why C is so easy to code in. Its very consistent in how things are done, to the point that once you get a hold of it, it becomes second nature.
It's not the acronyms that should be replaced with common sense. It's the 'follow blindly'. Know good principles and when (not) to apply them. Acronyms help to convey a principle (or set of principles) quickly.
@@Excalibaard do they really help? Check RUclips or literature. Most of the text, time and effort is spent explaining when NOT to use these principles.
id say abstraction isnt generally a tradeoff. but also i am a functional programmer so maybe i am the wrong person to ask when applying DRY to other paradigms
Great video. I feel like a lot of other videos on the same topic do not properly examine different cases where this principle may or may not apply.
I feel this video could've a little more examples in code specifically, but this is by far one of the most enjoyable videos I've seen on coding practices! I love the illustrations, the examples, and how (mostly) DRY the video was! Good job, be proud.
We live in the era of AI assisted code. Readability is more useful than DRY. They are not the same thing.
Its honestly just easier to write the code as verbose or as concise as you want it, as long as its easy to understand.
This is why C is so easy to code in. Its very consistent in how things are done, to the point that once you get a hold of it, it becomes second nature.
nice video man! There is a phrase from Sandi Metz that I love and live by:
Having duplicate code is far better than a bad abstraction.
If all these acronyms can't be followed blindly, why don't we replace them all with just common sense?
try it
IMO it's about the ease of remembering the acronyms as links to principles of common sense, and to make it easy to remind someone of them
"Common sense" is a fallacy. You don't blindly trust common sense, as it can be subject to your own prejudices and biases.
It's not the acronyms that should be replaced with common sense. It's the 'follow blindly'.
Know good principles and when (not) to apply them. Acronyms help to convey a principle (or set of principles) quickly.
@@Excalibaard do they really help? Check RUclips or literature. Most of the text, time and effort is spent explaining when NOT to use these principles.
5 stars for this one. I also know it as don't repeat behavior, but I like don't repeat knowledge also!
Thanks for this high quality content (I just suscribed) 👏👏👏
Nice video, looking forward to more SE content
loved it ♥♥
I really enjoy your format
Great video
Pretty cool video which software did you use to create the animations in it?
I create the animations with Motion Canvas (motioncanvas.io). You write the animations in Typescript then export as an mp4.
id say abstraction isnt generally a tradeoff. but also i am a functional programmer so maybe i am the wrong person to ask when applying DRY to other paradigms
That's not what the rule of three is, but that's generally what you should probably do.
unfortunately you'er right 😔
this is WRONG 😡 writing DRY code means you take great care to not get it WET 😡
Cringe takes
Cringe comment