I think this is more a critique of the industry rather than frameworks. It's how companies like to constantly adopt industry "standards" instead of hiring engineers to create the specific domain framework. A lot of times this does work, even most of the time but in the short term. In the long term it devolves into what the analogy with hammer factories is pointing out. It becomes too wide of a net that tries to solve too many domains. Then companies change what "engineering" means and it becomes a glorified product owner that knows programming but only to the extent they can use the tools.
Comments
I think this is more a critique of the industry rather than frameworks. It's how companies like to constantly adopt industry "standards" instead of hiring engineers to create the specific domain framework. A lot of times this does work, even most of the time but in the short term. In the long term it devolves into what the analogy with hammer factories is pointing out. It becomes too wide of a net that tries to solve too many domains. Then companies change what "engineering" means and it becomes a glorified product owner that knows programming but only to the extent they can use the tools.
This is an old, recurring post. To me it appears to have been inspired by IBM's various Java tooling from the 1990s.