The most powerful mental models are hierarchical: simple at a high level, but highly precise when you need to zoom in.
Show this thread
-
Good software APIs should reflect the mental models of domain experts: the syntax should match the most intuitive and most effective way to think about the underlying problem.
Show this thread
A side effect is that good APIs are modular and hierarchical -- they feel simple at a high level, but they are precise & expressive when you need it.
-
-
Tools are a reflection of how to think about problems. Good tools are shaped by good mental models, and in turn, they shape the way of thinking of their users.
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
This Tweet is unavailable.
-
The problem with any hierarchy is the limitation that there is only that one hierarchy. Like when one folder structure makes sense but a particular file might be useful in 2 different locations. Likewise, couldn't a feature be usefully referenced by more than 1 API endpoint?
End of conversation
-
-
-
Sometimes though, you have classes of different but similar problems Ideally, you should be able to use the same underlying hierarchical structure with different entry points. Rather than optimizing only for domain experts, you might be able to similarly support novice intuition
-
The problem with any hierarchy is the limitation that there is only that one hierarchy. Like, when one folder structure makes sense but a particular file might be useful in 2 different locations. Likewise, couldn't a feature be usefully referenced by more than 1 API endpoint?
End of conversation
New conversation -
-
-
Like keras
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.