Earlier quoted context omitted.
Sure you can. Plenty of 16 year olds have written say windows managers that thousands of people use -- that's production quality code. Your second argument is circular -- I'm saying a valid research goal should be to write solid and useful code, and then explain it. For example, you could write an OS kernel or kernel subsystem to fill some particular part of the design space. A great but rare example is what the auth…
All I mean is that fixing non-essential bugs, making your code pretty, worrying about small performance regressions, writing thorough documentation, polishing the user interface, porting your code to N platforms, dealing with copyrights and patents and trademarks, ensuring good distribution of your code either by selling it or making packages for major distros, and taking care of your users generally doesn't help you…
I'm saying it would be better for society if the academic culture emphasized the craft of coding, rather than solely "new ideas". The whole point of this article is that the emphasis on "new ideas" incentivizes fraud.
Academic culture changes faster than you think. I expect that the structural changes caused by online courses will have a big effect in the near future.