3 ms·
https://web.stanford.edu/class/ee384m/Handouts/HowtoReadPaper.pdf https://web.stanford.edu/class/ee384m/Handouts/HowtoReadPape... Keshav knows what’s up. I te
by hprotagonist 5y ago
https://web.stanford.edu/class/ee384m/Handouts/HowtoReadPaper.pdf https://web.stanford.edu/class/ee384m/Handouts/HowtoReadPape...
Keshav knows what’s up.
I tend to read the abstract, figures and captions, conclusion. Then i know if it’s worth really reading it, at which point i print it out and break out a pen.
if it’s really REALLY worth reading, ipython usually comes out to play, too
- pilotneko 5y ago+1 for How to Read a Paper by Keshav. I have been using this method for the entirety of my academic and industry career. Now that I run a Data Science team, I have all my new hires read this as part of onboarding. I'll just note that this pairs wonderfully with the Whitesides paper on Writing a Paper (https://gmwgroup.harvard.edu/files/gmwgroup/files/895.pdf https://gmwgroup.harvard.edu/files/gmwgroup/files/895.pdf), which is also required reading for my team members.
- hprotagonist 5y agoI like Kording, 2016 (doi.org/10.1101/088278) https://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1005619 https://journals.plos.org/ploscompbiol/article?id=10.1371/jo... too, for the output side.
- rramadass 5y ago+1 The same technique with necessary modifications is also applicable to figuring out whether it is worthwhile to completely Read a Book. These days Books have so much unnecessary filler that a lot can be skipped with no loss of information/knowledge. PS: The same author has also written two great books on Computer Networking; 1) An Engineering Approach to Computer Networking 2) Mathematical Foundations of Computer Networking