I hope the next evolution in software development includes caring about what your stack traces look like. Pattern based development is especially noisy that way. By the time you find a value going wrong you’ve forgotten why you needed to know that.
Lately I've been seeing "A Philosophy of Software Design" by John Ousterhout making waves with more experienced developers, and I definitely think it's going in the right direction of having richer abstractions and focus on DX rather than forcing the atomization of source code.
I’m currently suffering through nested serializers and business objects that have too much custom metaprogramming.
What’s worse: some of those would have been trivial when written in a more direct manner and would benefit from no-code tools.