After further thought, because overarching opinionated frameworks sometimes aren't the answer.
From an architectural POV, sometimes frameworks dont solve all your problems, and sometimes they make things harder for you by going against the grain of how your problem domain actually wants to be architected.
Knowing the basics of good software design and how to not use a framework if you're not able to has a lot of merit.
Some domain driven development can actually be idealized as you building your own framework of the problem domain. Why complicate that by adding an additional layer of infrastructure?
It really does depend on the project and evaluating the framework.
From an architectural POV, sometimes frameworks dont solve all your problems, and sometimes they make things harder for you by going against the grain of how your problem domain actually wants to be architected.
Knowing the basics of good software design and how to not use a framework if you're not able to has a lot of merit.
Some domain driven development can actually be idealized as you building your own framework of the problem domain. Why complicate that by adding an additional layer of infrastructure?
It really does depend on the project and evaluating the framework.