yo @JoshdelaRosa1 @jimmylovestea what are the 10 crack commandments for data science

—
MikeJackTzen (@MKJCKTZN) December 01, 2017

 It’s the ten crack commandments, what? homie can’t tell me nothing about this code Can’t tell me nothing about these #rstats

Number 1, make a function from a script. Everyone knows we’re to busy to be copy/pasting shit

http://adv-r.had.co.nz/Functions.html

Number 2, never let ’em know your data manipulation moves. Don’t you know Bad Boys move in silence and violence?

Number 3: never trust point-o-five p’s, your moms’ll set that ass up, properly gassed up, hoodie to mask up, for that fast buck

https://www.nature.com/articles/s41562-017-0189-z

Number 4: I know you heard this before “Never compute high on your own CPU supply”

Number 5: never store PII where you rest at

https://www2.census.gov/foia/ds_policies/ds007.pdf

Number 6: that goddamn STATA*? Dead it You think a crackhead paying you back, shit forget it! (*STATA/SAS/SPSS)

https://thomaswdinsmore.com/2018/03/07/sas-is-on-the-brink-of-something/#comment-10243

Numero Siete: this rule is so underrated Keep your training and test set completely seperated Money and blood don’t mix like two…

https://statistics.stanford.edu/research/estimating-error-rate-prediction-rule-improvements-cross-validation

Number 8, always keep survey weights on you. Them cats that squeeze your guns can ask what population your stats generalize to

https://www.statschat.org.nz/2016/10/25/oversampling/

Number 9 shoulda been Number 1 to me: If you ain’t gettin’ representative samples stay the fuck from police data

https://www.vox.com/2016/7/11/12148452/police-shootings-racism-study

Number 10, a strong word called Bayes-i-an Strictly for live men, not for freshmen

https://projecteuclid.org/euclid.aos/1176346785

#RIPBIGGIE