To put it simply, this reflects an amateur understanding of frameworks. I know where the author is coming from, because I've been there/done that/tried that. It sounds nice on paper, but experience has shown that this is a poor way to approach software development.
I see this kind of mindset with developers who think only about code, and not about solving problems at scale with other people.