> Yeah I think that, though experienced programmers tend to understand what makes code good, they're often bad at expressing it, so they end up making simplified and misleading "rules" like SRP.

I mean, I'm not saying that those approaches are always wholly bad from an organizational standpoint either, just that there are tradeoffs and whatnot.

> Some rules are better than others, but there's no substitute for reading a lot of code and learning to recognize legibility.

This feels very true though!