This reminds me of a striking example during our UI design class, which eventually led me to conclude that there is no intuitive design of anything, unless you can make specific assumptions about the users.<p>You have a steering wheel, and turn it to the right. What direction do you turn? It's such a simple question. And if you're used to a car, or a bike, it's so easy to answer. Turn right, go right. Well except every captain with his boat will tell you they will go left.<p>And there are so many examples of this if you look at them. Our monitoring has a lot of graphs, but why would a rising or a falling graph be good? If it's latency, you want it low but not 0, because 0 would be weird. If it's available capacity, you want it high, but too high is right out as well, since it's a waste. In some cases, we need ports open because we kinda need to answer productive HTTP requests, in other cases, it would be rather silly to expose elasticsearch to the internet.<p>Intuition and intuitive meaning is such a hard thing.