Perhaps the reason is that the actual production code is an unholy mess that they'd be ashamed to show?<p>Many times during my career, I've had to deal with those who profess to know the "right way" of doing things. They'll throw acronyms like DRY and YAGNI at you all day. They'll go on and on about patterns and "best practices". Yet when it comes to writing actual production-grade code, they often produce the worst of the worst.<p>This behavior has, in my experience, been extremely prevalent within the Ruby community, and with the JavaScript community to a lesser extent. So I wouldn't be at all surprised to see them making all sorts of recommendations, without ever backing it up with real-world code.