I started learning C at 11 and at 13-14 had software developed that assisted in reverse engineering and debugging of applications. These days that knowledge see

I started learning C at 11 and at 13-14 had software developed that assisted in reverse engineering and debugging of applications. These days that knowledge seems fairly trivial to me, and it isn't fundamentally complicated. Now with more understanding of theory and algorithms, it would be a lot easier to build much more useful tools like something that is as simple as dataflow analysis -- something I couldn't have fathomed at 14. Or binary instrumentation. Similarly, I had done socket work and reversing proprietary protocols, and I didn't consider any of that groundbreaking (nor was it substantially marketable). To walk into a field like AI and summarization which isn't infantile and outdo Ph.D. level experts at their own theory -- that's something you didn't do, nor did Nick, nor does anyone. It just doesn't happen, and hasn't in any subject with a similar depth of specialization as far as I'm aware. Not to say one can't make useful things and/or learn a lot very rapidly. I tend to understand the young, inexperienced people building games that sell well due to the frameworks available. And I understand how shareware could sell decently in a market that's widely open with lots of low-hanging fruit. But this situation is very different. That he built an application that grabbed parts of text and produced a shortened version by making some very rudimentary guesses about what's important perhaps. What's described -- not a chance.