Frameworkism: Senior Software Developers' Pit of Doom

This is the paragraph that stood out to me:

Writing frameworks feels good, productive, and best of all: it’s risk-free.

So before we start doing the hard work of actually having to write an application, why not spend some time considering what type of extension methods we’re going to need or what sort of data access patterns our application might use? We can submit lots of pull requests, get lots of green check marks, and even have unit tests to cover how our framework works so we get good test coverage score! Sure looks like productivity to me!

There was a Stanford study recently published here on HN stating that 10% of developers "aren't doing anything" and part of the measure was pull requests. Based off this paragraph from this article, I'm wondering if perhaps those 10% aren't perhaps the better developers? It would be kinda funny, in a sick way, if companies used pull requests to measure developer productivity and ended up letting go of their best developers.

I think this is a more general case of Big Idea Bike shedding. It could be a framework, but really it could be anything.

It's easy to get into thinking you're going to use this thing you're building for all future work you ever do in your life, while not actually doing any projects besides the framework or protocol or perfecting your grand plan to make all your stuff use UART over CAN transceivers on cat5.

The problem is that even if the framework is great.... it's still incredibly time consuming and others might not be interested.