Domain-Driven Design
We use DDD at the current company I work in and to be honest, I detest it so much that sometimes it makes me wonder if I even want to continue in the programming space (been at it for 20 years).<p>Don&#x27;t get me wrong, DDD has meaning and purpose, but some companies are applying it as a badge to be obtained instead of pondering the question, do you really need to rewrite everything following DDD?<p>In our case, simple CRUD APIs that in &quot;regular programming&quot; might take a couple 200 line files have turned into unmanageable nightmares in DDD that take you at least a couple of days of really intensive investigation to understand, because it have been divided in more that 25 files that hold 3 or 4 lines of code at most, with so many abstraction layers that it&#x27;s impossible for the best of us to follow in one go.<p>Now, you could make the argument &quot;You Are Doing It Wrong(tm)&quot; but since I&#x27;m just a drone in this specific scheme and there&#x27;s no wiggle room for anything (the team is quite inflexible on this) I have to follow it to the letter.<p>Just giving my two cents, again, not depreciating DDD, it has its purpose but in my opinion, it&#x27;s for very specific projects.