Sorry, didn&#x27;t mean to be rude. I considered it an observation. If you go to a university and ask a 2nd year student what he thinks about that topic he will tell you exactly that: Read some guide about how to do good usability and then just implement it that way. I think you need to have experienced that, putting a lot of energy into making a usable tool and then having users running into such kind of errors that you haven&#x27;t been able to forsee yourself. Only then can you understand that it&#x27;s not about not getting the guide but that the underlying problems that result in bad usability often are in other areas (like not enough testing, like not looking into the libraries one uses, like not fixing bugs in a way that improves the bug&#x27;s situation as well as the corresponding error messages). It is less about &#x27;what to implement&#x27; (clear to most devs) it is more about &#x27;how to implement it&#x27; (often completely ignored topic).<p>In that regard I hope I can make clear why it is not necessarily rude to tell someone that they haven&#x27;t made the experience. I have certain assumptions about climbing mountains, but I have never done that so quite a few of these assumptions will be wrong or not about the actual points you have to deal with while climbing. I need to be aware of that, though. Otherwise I will a) think that I know everything there is to know about that topic and b) I will think I can give advice to other people how they should do it.