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
+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.
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
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