Objectively your application has already been designed by the framework you choose. It tells you how to do and where to put most things and it also does all of

Objectively your application has already been designed by the framework you choose. It tells you how to do and where to put most things and it also does all of the heavy lifting, a.k.a. actually doing something useful. The design the application developer needs to be concerned with is how to split functionality into reusable components where it's needed. I mostly see big fails here: a lot of kind of best practice theater, but what you end up with are very complex components doused with concrete. I also see some straw man arguments, e.g. > Developers dislike design because it's time-consuming. I've never met a developer who doesn't like to design. I'd say the vast majority of developers even if tasked with something as simple as creating a button first try to craft a universal solution that can somehow be reused. Instead the correct design methodology most of the time is called KISS. You can always make it more complex later, but making it simpler is usually a lot more difficult.