This is fantastic. DARPA gets it. I look forward to whatever fruits come from this labor. Maybe one day I won't have to look at stack traces and reverse engineer 3rd-party dependencies to figure out why things are breaking. Maybe one day error messages will have explanatory power. Maybe one day IDEs will understand abstractions other than ASTs and types and instead will understand things that convey human intent that is not so closely tied to rigid constructs like type systems. What a wonderful world that will be.
> Maybe one day error messages will have explanatory power
I firmly believe that closely integrating the raw ML internals with the user experience will yield tremendous rewards.
The coding experience, with the stack trace debug experience loop (get stacktrace -> google -> stackoverflow.com -> try a new thing) could be vastly improved, and be made to be like an Akinator session [1].
How about having the IDE's console output be integrated in ML pipelines? You would have boxes with questions and suggestions like:
* Please select the words in the console output that are not supposed to happen.
* Is you current goal related to the following tag: a) library_upgrade, b) first_time_library_addition, c) <tag search box>
* Please describe with tags and words the context you are in.
* Go read this stackoverflow page. Did it help?
* I see you have been doing x and y, and getting these errors. Would you be interested in this tutorial?
* Last week you had this problem. It is resolved? What things (urls, boxes I presented you, etc) did it?
* Here is another context: eclipse, java, email, library_upgrade, ConcurrentModificationException. Are you having the same issues?
* Here are statistics about people being in the same context are you are in. Here is also the top remark they have said about it.
* Here is a decision tree node your context is currently in. Here are all the child nodes (lets you explore the tree without tainting your current context)
* Would you like to do some semi-supervised clustering for trying to tie your current context to other contexts?
And then have the dataset be openly accessible, with third party being able to provide boxes, and publicly emit new features, and all boxes being rateable.
With it implementing the base stackoverflow feedback loop, it would yield a user experience superior or equal to it.
