Good interface design is interactive. Programming expects users to describe *exactly* what they want, w/o interactively requesting more info
This is bad. We need code editors/languages that will comment on likely gaps between what was *actually* specified and what was *meant*
-
-
As a designer of APIs, there are many such situations where I would like to be able to interactively guide users; programming is inflexible
-
No matter how much thought we put into APIs, it remains that programming, as a medium, is fundamentally flawed. Why such disdain for users?
- Show replies
New conversation -
-
-
Critical for further automation of programming! People imagine a PM sending a giant spec doc to an AI coder, but actually will be a chatbot
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Doesn't it just mean "denote intent, not content" for naming things? Which ultimately returns to higher-order abstractions (function/class)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
There is a real opportunity for training helpful error messages from document editing histories.
-
Compiler/IDE trained to recognize common failures of development, suggest shortcuts in response.
- Show replies
New conversation -
-
-
Strongly typed languages help so much to close this gap, yet so many people refuse to use them.
-
They are the opposite of what he is asking, hehe. He expects things that can infer what was meant, not things that require even more details
- Show replies
New conversation -
-
-
I think Elm-lang takes a step most in that direction.
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.