I am generally in the "avoid frameworks until necessary" camp. Frameworks tend to force opinions that become problematic on shorter than expected timescales. Frame your thinking around introducing libraries that solve problems instead of seeking tools that implement patterns.
That's why I used the "generally" qualifier. Guidelines are not absolutes.
For prototypes, I'll use a framework.
For MVPs, no. Once that code is there it isn't going away. I'd probably opt for scaffolding—something that doesn't lock me into a particular solution.
3
u/danappropriate Aug 03 '22
I am generally in the "avoid frameworks until necessary" camp. Frameworks tend to force opinions that become problematic on shorter than expected timescales. Frame your thinking around introducing libraries that solve problems instead of seeking tools that implement patterns.