Cuz they espouse advice without having proven it in practice. When I say at scale, I mean they literally haven't shipped any software of note, I don't mean soft

Cuz they espouse advice without having proven it in practice. When I say at scale, I mean they literally haven't shipped any software of note, I don't mean software that's getting hit by an arbitrary number of req/s. Why I think this matters? They haven't demonstrated that their rather arbitrary list of Good Things help make successful software. Also, some of the advice is just provably nonsensical. Like "uncle" bob says the "ideal argument's number for a function is zero (niladic function)" which is absurd. It either means your function is impure, or is literally a constant. Most of it is just very shallow stuff that's mostly applicable to Java/C#/OO languages. A lot of the patterns might even be considered antipatterns in other languages. I just don't find stuff written by these guys very insightful or useful.