For example, a former employer of mine had problems reported with an internal search facility used by a branch of the customer service team. A coworker and I shadowed members of this team (ala contextual interview) to learn about their work and workflow. We were very interested to find that each user of this system had formed their own folk theory about the idiosyncrasies of the (very difficult to use) existing software, theories which let them get their jobs done. These theories had little to do with the inner workings of the software machine and everything to do with the tasks to be accomplished.
As such, creation of folk theory happens automatically in virtually any environment where humans use tools and processes. Even when this theory is backed by "science" or "inside knowledge", what emerges is still the working practice, mental models, and language forms of a folk theory. Back to the article's point then: the idea of invisible interface is problematic because it denies the formation and elevation of culture (folk theory) that will naturally form around an interface.
This need for intelligibility of the inner workings of the
technology, rather than simply keeping it invisible,
echoes Chalmers et al.’s work on “seamful design” [4]
which is exactly what the blog post is advocating.
The study linked to in the sentence points out that folk theories, while “not completely accurate accounts...can provide people with explanatory power, can guide behavior surrounding use of the technology, and can allow people to make predictions about how a technology will function under certain conditions.” [1]
These heuristics, though not perfectly accurate, can work for most of the user's use cases. Intervention is called for only when the practical implications of the folk theory are misleading.
[1] http://www.cc.gatech.edu/grads/l/ledantec/files/poole-ledant...