Interesting video. I can totally see why comments are disabled for it, because adepts of "Clean Code" would lose their mind watching it.
I started coding in PHP with having 1 large file doing everything, and it was working completely fine for my purposes at the time. Even when I started splitting code into separate files for a full-scale website, I still was not using polymorphism or inheritance, because I did not feel the need to.
The only reason I started using them was... To utilize full capabilities of an IDE (JetBrains PhpStorm) and essentially follow the D.R.Y. rule. In 3 (or is it 4?) years I've been using PHPStorm I am still not trying to follow those "Clean code" conventions. And I think this video explains it quite well "why": because I can't predict things.
Truly following "Clean Code" requires you to predict how you app will grow. Don't know about other coders, but I have refactored pieces of code so often, that I am well aware, that you can't really predict a thing. Or you can't rely on your initial predictions.
"Clean Code" adepts will be crazy about defending the concept, saying that these rules will make code more maintainable. Yes, code maintainability is a real thing, even when you code alone, but you know what else helps with that? Comments.
That is not to say that the 1st video is necessarily against the concept, no. I mean, the testing is done on something extremely simple, but... It does show you the cost of strictly following these rules. And a good developer needs to know the cost of things. I mean, every time you write a function in a certain way you are making potentially dozens (if not more) of decisions, and you make them fully aware of the potential downsides. Same should be applied to any coding rules, as well.
