I believe that the Rich Hickey’s mantra “simple is better than easy” applies very well to UIs. A lot of the times UIs try to hide complexity by making it “easy

I believe that the Rich Hickey’s mantra “simple is better than easy” applies very well to UIs. A lot of the times UIs try to hide complexity by making it “easy” to do common tasks, but the underlying complexity is still there and rears its ugly head when you inevitably bump into an edge case, then you have to learn all that complexity (or as is often the case - rage quit). A good example is Amazon software in general - from their shopping software to AWS console - all great if you’ve done it before and follow their guided path, but if you want to understand what will _actually_ happen or to do a specific edge case well then you better have a lot of nerves and patience. Seen a person actually brought to tears by a shopping experience were she fell outside of a happy one click sale path and had to do some amendments, with some significant money on the line. She just felt powerless because suddenly an “easy” experience turned bad and now she had to understand _all_ the minutia around sellers, shipping and refund policies. Not a pretty sight. Had the underlying principles been a little less convoluted, and actually exposed, then a user could successfully navigate even some edge cases as then he would have at least some tools at his deposal. Right now UIs tend to drift to “click and pray” category, where you identify what’s the several common scenarios and just cover those.