This is also another winning point of the framework: Frameworks save you time, and allow you to write less code. By writing less code, it is much easier to unde

This is also another winning point of the framework: Frameworks save you time, and allow you to write less code. By writing less code, it is much easier to understand what your program is doing, and change it as requirements change. When you work without a framework, you invent your own framework. It won't be as well thought through - guaranteed. When changes come in, the sheer amount of code means mistakes will be made and your code will slowly turn into spaghetti. If this is a custom FFMPeg conversion service - totally worth it. If it's CRUD, like how 90% of apps are CRUD, then it's probably a mistake. As I told another programmer, using a framework doesn't mean you are a "semi-skilled" programmer (what elitism). It means you know you aren't special, you aren't smarter than other programmers, you know your own limitations, and know that using a framework other people understand (and keeping the amount of code to a minimum) is the best for your company and the project.