> it would be an awful ux if words needed to be added explicitly to the dictionary. What I'm learning today is that there is no such thing as best UX practices

> it would be an awful ux if words needed to be added explicitly to the dictionary. What I'm learning today is that there is no such thing as best UX practices. Some people are clearly adamant that having to add words explicitly is awful. After all, the phone should be able to figure out what is wanted, right? Other people are just as certain that having the phone implicitly add words using any specific rule will fail often enough that it's obviously worse UX to try. I find myself in sympathy with both camps. I would like my devices and environment to just know what I want and do it without my having to explicitly direct actions. Unfortunately, it doesn't seem to be working out that way for a lot of areas. Instead, we have a mishmash situation where devices and apps try to do what most people want, and fail fairly often for a given user (unless I'm a major outlier). Ten years ago, when my computer failed to do what I expected, I understood that I'd failed to use it properly. I read documentation until I understood the failure or, at least, had some idea of what I might have done wrong, and tried again, and eventually I would understand the system. Now that the system is supposed to understand me, I've noticed two effects: First, detailed documentation of user interfaces is incredibly scarce. I wonder if there's a perception among other developers that if you need documentation, the UX has failed, and therefore the most direct route to apparently better UX is to have less documentation? Second, I find that partly due to the apparent complexity of my phone (or perhaps personification of it), I'm more likely to just swear at it and complain about it than to actually try to understand what I'm doing wrong.