3 ms·
You might be agreeing with me, and perhaps are missing my point: more people, especially statisticians, will be engaged in the programming and programming-like
by mkyc 17y ago
You might be agreeing with me, and perhaps are missing my point: more people, especially statisticians, will be engaged in the programming and programming-like tasks that are required to work with ever-increasing data. Not structured-SQL data, but raw and ugly natural-language and legacy-format data. Many programming tasks in the future will be about data, and excel-like "Illustrative" programs are very well adapted, even if not Turing-complete (Interesting discussions on the turing completeness/incompleteness of even something like Excel: http://www.c2.com/cgi/wiki?ProductivityRant http://www.c2.com/cgi/wiki?ProductivityRant http://news.ycombinator.net/item?id=429477 http://news.ycombinator.net/item?id=429477 ). Illustrative programming is just dynamic programming plus immediate feedback of program results - perhaps the ability to click on a GUI element, and change its associated code in realtime, perhaps just the ability to change how a data-point is calculated. The tools will be different.
Turing-completeness will always look like Turing-completeness, but this is hardly interesting or relevant. I think that your claim about productivity is entirely false (see something like http://www.cs.umass.edu/~yannis/law.html http://www.cs.umass.edu/~yannis/law.html ), but that's beside the point of my post.
- fauigerzigerk 17y agoI do agree with you that data analysis is of growing importance (it's what I do after all). But I object to inventing a new fancy term for what you describe as "dynamic programming plus immediate feedback". We had that for ages. "Illustrative programming" is just a classical case of a consultant inventing fancy marketable language. In Excel the illustrative parts are not the ones that involve programming in the sense of Turing completness. I think we need to use Turing completeness as a benchmark, or any interaction with computers can be called programming. And I stand by my claim that programming something like KWIC has not become much more productive in the past 20 years. You could do it in Perl or in Lisp just as easily in 1989 as you could do it today. Even in C it's not that much less productive to flip and sort a few words than, say, in Java. But productivity is admittedly a complex concept. Of course we have a much greater effect writing software today, but I think that has very little to do with the core techniques of programming. We may be more productive on average, simply because more people make use of techniques that fewer people were using in 1989.