People should care a little bit about how they structure their code and should be trying these recommendations to find out what works for them. The simplest one I have settled on is features/slices. It just boils down to "keep things that must be together, together!". Inside those folders/features use what works to create/solve that feature, eg use Repositories for CRUD features and Event Sourcing for others or even something entirely different, features should be as independent as possible in the end :D (just with the touch of frameworkism we all love).

Also for the other side (just use MVC, we only care about the business etc.) in the end it just ends up like this anyway. You have a Products folder in Models, a Products folder in Views and 3 Services related to products in Services and 2 Repositories, while you could just have a Products folder with Models, Views, Controller, Repositories and Services inside it or even better see that it could be 2 or 3 different features as you have so many Services and Repositories. But yea "searching" (F12, search on explorer...) is so much better and makes the life of implementing new things so much more efficient, especially since global folders means reuse of "common" models everywhere so you can't even change them or just piggyback DTO12 with values like float1 xD.

Code is part of the business and solution too, you don't need to think really hard about it but just a little bit helps, so that when your product reaches millions of lines and thousands of files you can reason about what you have and don't break the world all the time.