←back to thread

873 points belter | 1 comments | | HN request time: 0s | source
Show context
tines ◴[] No.42948564[source]
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?"

replies(2): >>42948628 #>>42950540 #
ryathal ◴[] No.42950540[source]
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.
replies(2): >>42950778 #>>42950894 #
1. tines ◴[] No.42950894[source]
I'd argue that's a poor way to say that, because "managing" complexity tends to mean "taming" or dealing with complexity in a good way.