When navigating through Line-of-Business (LoB) applications, you'll notice that most try to follow Clean Architecture and all its layers. I blame the tutorials and scaffolding tools that make it clear that you must separate your logic into Application Services and Domain Services. I don't have much problem with the separation itself, but the unnecessary layers and numerous rules, just make the software way more verbose than it should be. I caught myself discussing and losing time, over and over, deciding if a class should go to the Application or Domain layers. Let's break the paradigm The first step to thinking differently is to ask why we do the things we do. The reasons we have layers is to provide organization and fulfill abstractions. A simple example of organization is separating all of your classes in the invisible layers of "types". I'm sure you named folders like Classes, Models, Requests and so on. Why are we abstracting by type? Why do we need abstractions then?…