I'm wondering where to draw the line between situation 1 and 2. At 5 lines of code? 10 lines?
-
-
Replying to @pattithepotato @o_guest and
Where you would have to cite in in a research paper as it is no longer common knowledge ?
1 reply 0 retweets 1 like -
Replying to @mrhunsaker @pattithepotato and
I dunno, it might be "common knowledge" how to calculate the Gini but if you stole my code, you stole my code:https://github.com/oliviaguest/gini …
2 replies 1 retweet 0 likes -
Replying to @o_guest @pattithepotato and
I agree. But I would have to cite your repo. I guess best idea is to cite wherever you got code since you had to look it up.
1 reply 0 retweets 1 like -
Replying to @mrhunsaker @pattithepotato and
Yeah. I link to StackOverflow comments when I use their functions, even though I know that like me they probably wouldn't care, I also don't wanna pretend I came up with their functions either.
1 reply 1 retweet 2 likes -
Replying to @o_guest @mrhunsaker and
That may be too extreme for my own practice, but then again, usually only a small snippet is relevant for me. That said, if a significant portion of my code was inspired by another code, I will cite even if it no longer looks like the original.
1 reply 0 retweets 1 like -
Replying to @pattithepotato @mrhunsaker and
I'll show you an example where I link to SO. I took this whole function and put it in my code: https://stackoverflow.com/a/22376126
3 replies 0 retweets 1 like -
Replying to @o_guest @mrhunsaker and
I definitely don't not use warnings.filterwarnings('ignore'), so good for you for caring about warnings

1 reply 0 retweets 0 likes -
Replying to @pattithepotato @mrhunsaker and
Really dangerous with pandas.
3 replies 0 retweets 0 likes -
Replying to @o_guest @mrhunsaker and
Not sure about "dangerous," but perhaps cumbersome. What dangerous issue(s) are you referring to? In any case, I was just joking. I add the ignore warnings at the end after I know the code runs.
1 reply 0 retweets 0 likes
I linked to it. Serious problems if you ignore SettingWithCopyWarning.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.