Hello,
comments are moderated on his blog… So I don’t think you will see my answer or yours.
Here’s what he sent me by mail when he had to “accept” my comment on the blog :[quote=“Evangelos Georgiou”]Hi Christophe,
Im sorry my blog post upset you so much. I did not in any way claim in the blog post or the video tutorial that the additional library was my own.
It is unnecessary to make any claims about my intelligence, you dont know me!
To be honest I didnt remember where the drivers were sourced from, Im more than happy to make a reference if you provide the link.
Regards,
Evangelos Georgiou[/quote]
“To be honest”
The fact is that he has removed my name to put his references in the code. This is not fair, and he can’t claim for “honesty” in any way after that.
It’s really not hard to write somewhere “based on the work by XXXX” or “inspired by XXXX on tinyclr.com”.
I don’t know if it’s worth a public lapidation, but I also don’t like this kind of plagiarism. Maybe he’s young and only needs to be taught the correct way of using others’ code ?
About the discipline for commenting, I don’t have it all the time In fact, in my last code entries, it’s not as documented as the first ones. The main reason (which I know is not a good reason) is that (I think) code length influences the number of points you get when you post a code snippet.
But, comments are not really code, even though it’s very useful. So I don’t want to look like I “need” points or I abuse the system.
Some portions of the code may not need more than one line, for example. Say, the Cursor(x,y) method is pretty straight forward and should need a mere 20 lines but only 1.
But still, in the case of code that would go in a public assembly (which is not necessarily the case, btw), I think that commenting is a good idea. And it’s not that hard with the very good Ghostdoc plugin : SubMain / GhostDoc - Painless Help Documentation