Lots of hype about event sourcing and CQRS, usually in combination. 99% won't need it. Has the potential to ruin your team and even company unless you have a well-above-average engineering team.
DDD strikes me the software version of Agile sometimes. The ideas and philosophy behind are good, but ends up being taken as a silver bullet. If you do this you will have a good architecture and your software will be well architected.
Especially in the .NET world i've seen DDD being branded together with CQRS as "Clean Architecture" which in reality turns out to be a mess of layers and separations.
I map it the same way to caps lock and experience exactly the same you describe. I noticed after the last patch a few weeks ago it went away for now. Been driving me nuts until.
Plenty of these systems have caught some focus the past year. A different question might be - why do developers not say no to work on this type of software?