Software development topics I've changed my mind on

How does

> There is no pride in managing or understanding complexity

interact with

> If I think something is easy, that's a sure sign I don't understand it.

? Is it implying that you must understand the irreducible complexity, but mustn't take pride in that understanding? Or is "difficult" the opposite of "easy" here, rather than "complex?"

It's saying you don't need to be proud of your app that has multiple layers of abstractions to be immune to every possible change. There are hard problems, but the most complex solution is rarely good or best.