5 Reasons Bad Techies Will Give for Not Using an Application Framework
See the original posting on DZone Python
I know what you are thinking, in this day and age who would not want to use a framework? But if you have enough confirmation bias, the internet will provide you with evidence. I have met at least a couple of tech leads who denied their teams the comfort of using a robust framework. One of them worked at a company which had raised more than $9M in funding rounds. Don’t make the mistake of thinking that companies that allow their leads to perpetuate such stupidity will quickly get lost into oblivion. Well, they eventually do but not without burning a lot of their investor’s money. Without further ado, if you are being sold this idea of not using a framework, here are the top 5 reasons that you will hear and the subtle undertones of incompetence that they carry.
5. Frameworks Are Complicated
This is one of my favorites. You would hear phrases like, "there is too much magic happening in there" or "setting it up will take a lot of time" or "it works while it works, but when it stops…" etc. This person is evading the responsibility of understanding the framework thoroughly. The person advocating to not use a framework because it’s complicated probably never understood the difference between Complex and Complicated. Of course, frameworks are complex, because they are created to tackle complex problems and reduce the complications which would otherwise result from bad design. They don’t even realize that there is a good chance they will indeed end up with a bad design because only 1 in 50 developers are able to define good abstractions. In short, you are being told, "I can’t wrap my head around this complexity yet, and I don’t think I will ever be able to make this work. So I’d rather let the junior developers toil away barebones. When they are stuck, it’ll be their fault."