News for hackers. Stuff that matters.
Re:Modeling How Programmers Read Code by seanmcdirmid on Sunday July 07, 2013 @12:03AM (#6000994)
That's why the program should be expressed as a conversation! We don't know what we want so we should start vague, get feedback, provide clarifications, and so on. The conversation with the computer must be a two-way thing!
Re:Modeling How Programmers Read Code by lifeisstillgood on Sunday July 07, 2013 @04:03AM (#6001452)
That's brilliant. Not in terms of some AI working out what a silver haired old grandmother meant but in terms of talking to clients - they could imagine talking to a computer and I am just providing that feedback.

Daily or weekly, feedback nice and quick

Re:Modeling How Programmers Read Code by seanmcdirmid on Sunday July 07, 2013 @05:59AM (#6001612)
The thing is, we probably don't need hard AI yet to do some of this. Yes, it must be a dialogue system, but we have those today. We already saw the movement in this direction with Hugo Liu's concept.net work, but for some reason no one has followed up yet. We are getting to the point with speech rec/understanding technology that someone is bound to try again soon.
Re:Modeling How Programmers Read Code by eli_gottlieb on Sunday July 07, 2013 @10:46AM (#6002145)
In general, we don't need Hard AI for much anything, and usually don't want it. Any specific problem you want solved will require some specific solution method or algorithm rather than the whole and entire "make a computer hold an adequate water-cooler conversation" thing.