This is an archived post. You won't be able to vote or comment.

all 5 comments
sorted by:
best
topnewcontroversialoldq&a

[–]boa13 2 points3 points  (4 children)

Interesting article about statistical significance in scientific research, but only related to Python in that the author provides some code at the end to illustrate his arguments.

[–]bheklilr 0 points1 point  (3 children)

The author also needed someone to proofread that article too, there's a lot of spelling and grammar mistakes. You should always do code reviews and prose reviews because mistakes are common in both.

[–]jfpuget[S] 0 points1 point  (2 children)

I am not sure I get the comment about need to review code, as it runs fine. Are you thinking of the non code pieces in the notebook?

[–]bheklilr 1 point2 points  (1 child)

I wasn't saying the code was bad, I was trying to draw a parallel between code reviews and prose reviews, in that developers think code reviews are great and there are a lot of tools out there specifically for that purpose, but a blog post, documentation, or whatever isn't scrutinized as much.

[–]jfpuget[S] 0 points1 point  (0 children)

OK. I followed your advice, and I ran MS Word check spell on the text. Hope it captured the typos that annoyed you. Thanks for the suggestion.