The idea is “x” framework provides a level of convenience that can make developers sloppy.
This often happens because frameworks tend to make developing easier. So easy we forget to take a step back and figure out how all the pieces come together.
If the framework is modeled on the model view controller (MVC) pattern. The convenience trap for developers is adding unnecessary amounts of logic into controllers or models. It’s easy to do and get the work “done” and out of the way if no testing is involved. Generally the problem with putting unnecessary amounts of logic in controllers or models is hard to test which subsequently causes the application to be brittle.
Oh looky here something database related this needs to go in a model or hey this interacts with the user’s input this probably goes in the controller.
The framework should not be the application, but a portion that compliments the development.
Note: The above generally applies to larger apps and not small apps that may have a short lifecycle.
How to mitigate the framework convenience trap?
- Write tests for the application. If tests are written chances are the structure of the app is designed better.
- Learn software best practices.
- Don’t code in a silo. Talk to other developers.
- Realize no one has perfect code and let someone critique your code. DON’T TAKE IT PERSONAL.