Re:Building a full-text search engine in 150 lines of Python...
by KAdot on Thursday March 25, 2021 @04:39PM
(#26585096)
The article looks suspiciously similar to https://artem.krylysov.com/blog/2020/07/28/lets-build-a-full.... Very similar examples, code and structure.
[ Parent
| on HN ]
Re:Building a full-text search engine in 150 lines of Python...
by jeroenhd on Thursday March 25, 2021 @06:07PM
(#26586132)
Does it? Both are implementations and explanations of a well-known algorithm. Most articles on quicksort will also look alike, but there's no reason to assume the author has plagiarized anything.
Re:Building a full-text search engine in 150 lines of Python...
by google234123 on Thursday March 25, 2021 @08:59PM
(#26587704)
Compare "def analyze" and "func analyze". It's obvious this article was copying the other.
Re:Building a full-text search engine in 150 lines of Python...
by pmiller2 on Thursday March 25, 2021 @05:11PM
(#26585429)
So? Wikipedia is one of the most convenient, large English corpora available, and I doubt there are many significantly different ways to write the bit of functionality that's built up here. I'm not sure if that's what you're meaning to suggest, or that there was some kind of plagiarism / inspiration going on here.
Re:Building a full-text search engine in 150 lines of Python...
by google234123 on Thursday March 25, 2021 @08:59PM
(#26587700)
I think it is plagiarize. Compare "def analyze" and "func analyze". Very similar.
Re:Building a full-text search engine in 150 lines of Python...
by yesenadam on Thursday March 25, 2021 @11:04PM
(#26588371)
I saw a case once, I forget where, when someone was accused of plagiarising from wikipedia and the truth was that they'd themselves written a large part of the wikipedia article.
Re:Building a full-text search engine in 150 lines of Python...
by diogenesjunior on Thursday March 25, 2021 @04:41PM
(#26585110)
Except that one is written in go and the other in python...
Re:Building a full-text search engine in 150 lines of Python...
by johnwheeler on Thursday March 25, 2021 @05:08PM
(#26585409)
Yes, but where's the attribution?
Re:Building a full-text search engine in 150 lines of Python...
by pmiller2 on Thursday March 25, 2021 @05:12PM
(#26585441)
How many different ways do you think there are to write this code?
Re:Building a full-text search engine in 150 lines of Python...
by dplgk on Thursday March 25, 2021 @07:52PM
(#26587178)
A billion?
Re:Building a full-text search engine in 150 lines of Python...
by argaba on Thursday March 25, 2021 @06:40PM
(#26586526)
Everything is a paraphrase of the original source - whatever and/or whenever that maybe from.
Re:Building a full-text search engine in 150 lines of Python...
by skapadia on Thursday March 25, 2021 @08:01PM
(#26587266)
Including our very own DNA...
Re:Building a full-text search engine in 150 lines of Python...
by boublepop on Saturday March 27, 2021 @09:14AM
(#26602047)
True, but it’s also common for people to acknowledge where their DNA came from.
You would likely be called out if you tried to hide that fact in order to seem more accomplished than your are. If for instance your dad is the owner of the company you are working at, you’d be rightfully be called out if you tried to hide the fact that your accomplishment is lessened by the fact that you copied your fathers DNA.
No one is claiming the author did anything wrong in copying the source material for his article. However it is wrong to not provide proper attribution, especially when it’s as easy as an “inspired by link” at the bottom.