>The cleanliness and "refactorability" of my code improved significantly when I drastically reduced the amount of subclassing I was doing.
>I wouldn't go so far to say "never subclass", but I'd say most of the time, you won't need to subclass.
Yeah, I would agree with that. A lot of OOP mechanisms like inheritance, or design patterns, get overused a lot. I'm not saying it's what you were doing, but I've seen it mostly in code written by newish programmers. It seems that once the concepts of OOP click in their mind, they get excited and eager to put them to work, so they use them where they're not really appropriate. I was definitely guilty of that, way back in the day. But once the novelty wore off, and I realized that I was just creating over-architected messes, I quit doing it.