I think that there is an issue with frameworks today. I am especially talking about web based ones. I am speaking mostly of web application frameworks, but the same can be said of data repositories (databases etc.) and many other things. We are seeing technology churn in this area. Or perhaps more simply people are changing the frameworks they use frequently. So frequently sometimes that I have seen frameworks changed midway through a project.

Many are open about the issue. Matthew Jones talks of the difficulty of framework selection (What is JavaScript Fatigue?) whereas Samuel talks of it be a natural order of things (Angular, React, and Javascript framework fatigue). It doesn't stop it being technology churn when a framework disappears overnight. Open Source Software (OSS) is not the solution for many enterprises either. They want their developers to develop business solutions. Not maintain frameworks.

The problem with technology churn, regardless of the technology involved, is that it leads to development in a vacuum. Almost by definition there will be a serious lack of experience and expertise. Little help is available, if anything, in the way of online communities or any other form of online help. I have been at the bleeding edge of some technologies and, whilst you can bring general experience to the table, I could not help feeling a bit of a charlatan. Whilst I have never claimed expertise under these circumstances, I did agree to deliver on something I was not certain of, nor could I be. How could I be so confident? So sure?<

But perhaps I am wrong. Perhaps the issue is not with the proliferation of frameworks and our lack of experience but with our attitude towards them. What is your attitude? Proliferation of what plagues your professional life?