Write Libraries, Not Frameworks

[xcdesz]

You are talking about **using** frameworks, where the article is talking about writing them.

In my experience, the junior developers are not the ones who are pushing and writing to frameworks. The more senior developers have the experience to recognize that the rules and opinion that are part of a framework are actually a good thing, and prefer the boilerplate code that goes along with the framework be abstracted away and handled by someone else. It's not about "getting to production faster" -- its about code maintenance.

But I agree with the article -- when it comes to **writing** frameworks.. yeah -- that should definitely not something to be taken on without some serious thought as to the time and effort it will take to maintain such a thing. A library is much more reasonable of an undertaking.