How to read research paper, textbook, long text content?
But I have issue with reading huge huge texts as you know in this case it will require too much time when I do this. Is there way to simplify this reading style?
eg-: of sth that I want to read is this.
https://static.googleusercontent.com/media/research.google.c...
It takes me 45 minutes to read 3 paragraph and comprehend it at least.
If I go that way, you can imagine, how long it takes me to read a research paper. Probably a week to read a research paper lol. Even reading articles in internet is a hassle for me if they are longer. If I just read what I need to learn it is easy as it will be few paragraphs but if I have to learn sth else long it is pain to me as I can't do it timely manner.
Are there any udemy courses that teach how to read textbooks for university students that you are aware of?
88 comments
[ 3.0 ms ] story [ 151 ms ] threadAnd if it doesn’t work out that particular day, that’s fine too. Don’t beat yourself up over it or try to force it. Just re-attempt pretty soon, like “later in the same day” soon, or “the following morning” soon- the key to more steady and fluid accomplishments of lots of little tasks is winnowing down the timeframe for little feedback loops.
tl;dr: you already know everything you think you need to do it :)
https://www.worldcat.org/title/how-to-read-a-book-the-art-of...
https://archive.org/search.php?query=how+to+read+a+book+adle...
https://libgen.rs/search.php?req=adler+how+to+read+a+book&lg...
Analogy aside, not all text is written to be read in a 45 min session. Set your mind that reading and absorbing content from a text book can take anywhere between 3 months to 3 years. Some concepts may take decades to really click in your mind. Luckily, the content in text books is usually broken down in chapters and sections for you, so consider each of those a "less text" content, and read "less text" every day. Set a goal of understanding a single section or chapter per day/week. At the end of a year you'll have read "long text" without ever reading much in a single reading session.
Research papers can be read in anywhere from minutes to a couple weeks. But if you are new to the field, you may have to read them over and over, and that time can extend to months until you understand the implications of what is written.
Don't rush it.
Either you have never read a research paper, or you are gifted, or you have been doing that for so long in your field that you forgot how hard it can be when you start.
However, among my colleagues (all very talented in their own unrelated areas) it generated a fair amount of consternation, because although they had a week to read it, none of them felt like they had a good grasp of it until after I had presented it. The key takeaways that had jumped out at me immediately were lost in the noise.
Whether or not a week is the right time, I can definitely empathize with taking more than a day to evaluate a paper, particularly in an area not very near to your own as there might be a lot of missing background to fill in. In contrast, my PhD advisor could flip through a paper in 30 seconds and pick up the key points it took me an hour to extract. In that sense, I really think that reading papers is a skill that can be trained.
[0]: https://drops.dagstuhl.de/opus/volltexte/2020/13109/pdf/LIPI...
You definitely don't need a week for just one paper. I wasn't even a graduate student. Papers are usually around 16 pages. It would take me a good 4-5 hours to read and digest things, and even longer when it was my turn to present a paper, but never an entire week... Professors go over these things even faster.
Most papers can be read in < 10 seconds ("not interesting, next"). Most pretty good papers can be read in 5-10 minutes. Very good papers might take a few hours. And so on.
I'm caricaturing, but only a tiny bit, this is how I read. And for good stuff, that I want to understand, a page an hour is (often) pretty typical for my first fairly thorough read.
I've written two textbooks, and in both cases I thought of the book as the distilled outcome from reading about a dozen very important papers really thoroughly
I can barely get myself to read anything long, even exams! Somehow, starting from the last paragraph, and sometimes even the last sentence, and going back, makes me actually read the text. This also worked with research papers (conclusion -> 1st paragraph). Maybe give it a try?
It’s partly because seeing the conclusions first triggers a “why”, that I then have to go back and discover in the previous explanations. Most research papers put the final conclusions in the abstract, but each subsequent section and paragraph also ends with intermediate conclusions. Read those first, then go backwards to find out why.
It’s also partly because it forces my mind to actively rearrange the knowledge coming into it, rather than having it all neatly pre-arranged by the author.
Maybe other things too, but for whatever reason it helps me be an active, rather than passive, reader.
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
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), which is also required reading for my team members.
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
I think it's the latter. I would suggest you to do some meditation.
Throwing an arrow in the air but it might be the case that your mind is wandering too much when you start reading. Doing some concentration practice will help.
Obviously, how you should read dense technical material will differ greatly depending on your goal.
For instance, if you are looking only for an answer to a specific question, you might prefer to do a sort of DFS on the paper. Read the intro material to get an impression of where in the paper the answer might lie, then go read those parts (in descending order of likelihood of containing the answer). A similar approach might work if you already know the area and are simply looking to see if the paper contains a particular result. Sometimes this process will still require some investment in understanding notation and terminology, but time spent doing this should be kept to a minimum.
On the other hand, if you intend to master the material and develop it further, then you might take a totally different approach where you prepare your own set of detailed notes on the paper (taking care to expand, in places where your own knowledge is lacking, techinical terms and concepts that are used in the paper but not explained using secondary references). This might also include working out many examples or thought experiments to help you internalize the logic and concepts. For a significant paper this process will take a long time, but it will be worthwhile if you truely want to understand the paper comprehensively and be able to build on it in a substantial way.
No matter your goal and approach, the point is that reading a paper productively is a systematic thing. Skimming technical papers lacksidasically is often a waste of time that doesn't produce value.
I am always on the lookout for papers that might help with something I need for work. I do a quick skim of papers and when I identify one or two that might be very useful, then I read them slowly and repeatedly. For me, the trick is finding material that is worth a lot of study time.
Remember that most people who write are still sounding out ideas when they write, so the final paragraph or final chapter of a monograph is where to start with most things. Then I read them in reverse order.
If it's professionally edited, you can read the first few parts because the editor will have uncovered any buried ledes and popped them up into the front matter. In journalistic writing, the opinion ("context") they were trying to freight the piece with is at the end.
If you're a university student you probably have access to a student support service that can assess you and advise you if that is the case. In the mean-time some people find using the [1] OpenDylsexic typeface helps and coloured overlays over text can be effective for some (Literally stick coloured acetate over what you're reading or change the font and background colours if on a screen). Other than that using various [2] notetaking methods will help with with both reading and retaining the knowledge. You're kind of already doing that with the slides BUT handwritten notes are generally more effective than notetaking on a computer.
[1]https://opendyslexic.org/ [2]https://medium.goodnotes.com/the-best-note-taking-methods-fo...
[0] https://annals.math.princeton.edu/2005/161-1/p10
And this takes a metric fuck ton of practice. There is no royal road.
IMO, you should probably start with easier material until you strengthen these muscles. Some examples of friendly CS texts that comes to mind are Programming Pearls, the C programming language, or the SQL paper by Codd https://www.seas.upenn.edu/~zives/03f/cis550/codd.pdf
I'd be curious what texts other people would recommend for someone who is a student getting a bachelor's degree in CS.
http://www-formal.stanford.edu/jmc/recursive.html
Full title is - Recursive Functions of Symbolic Expressions and Their Computation by Machine.
You could also consider talking to a mental health professional. I can’t diagnose you, but a few things you mentioned make me wonder if you may have a mild form of one of these:
* ADHD
* Dyslexia
* Internet Addiction
Or maybe reformatting the text with layout, font, font-sizes that work better for you?
Not suggesting either solves the problem, but the small experiments might help identify an issue.
I have also had problems understanding some research papers, but the example one you linked is pretty straightforward to me. Reading the whole paper would take me some time, but not 45 minutes for 3 typical paragraphs. And I'm not that great at it. That's why I'm seconding the idea that maybe dyslexia or something similar is in play here.
That said, sometimes you don’t need to comprehend all of the details. In those cases, use reading strategies that will let you tease out the main points quickly. Other folks in this thread have pointed to some good sources, so I won’t repeat them here.
Best of luck!
- Review: amass several papers related to the topic, either through search (e.g. Google Scholar) or through a survey paper on the topic.
- Filter: read the abstracts and decide which papers are worth skimming.
- Skim: read the introduction, skim the figures and their captions, and conclusion. This step is another filter; ask yourself whether diving into the technical minutia is worth it.
- Read: read the paper in-depth, taking notes in your manner of choice (which seems to be slides for OP).
- Reread: read and skim the paper a few more times until you could summarize it to someone else. Divorce yourself from the paper by reading other papers, and revisit it to contextualize its contribution.
- Compare: read similar papers (such as papers trying to solve the same problem both before and after the current paper) to get a sense of the whole space and range of methods tried to date. Also, look what later papers say about the paper under scrutiny.
Finally, reflect on how the various papers found in the 'Gather' phase related to each other: do they refine each other, refute, supersede etc.?
For research papers, I almost always start by reading the abstract and the conclusion, then reading related sections to answer questions I have about that. I'm not editing papers, or checking their validity: I just want to know what they're going on about.
Another thing is to ask whether you're reading the right document. For that GFS paper, I wonder if it's the right place to start learning about GFS. Ideally, you'd come to it with enough knowledge already that you don't need puzzle over every word. Are there introductory explanations? Youtube videos? Go over those first and come back later, and the paper probably won't be as cryptic.
For fiction, the best advice I ever got from an English professor, which changed my relationship with books, is this: if you don't like it, and nobody is making you read it, then stop reading it. Read something you can't put down instead.
In general, I think you haven't actually read something until you've read it twice. So, read it through once quickly, to get the idea, then read it again more slowly to understand it.
1. Just read A LOT. There is no way around it. If you push yourself to do this, eventually your mind will figure out a way.
2. Markup the text you are reading. I do this on an iPad with a stylus. I underline key points, circle important paragraphs, jot down a quick summary of lengthy thoughts.
Good luck!
It's never easy but it gets easier. Do it a lot.
Part of what slows people down reading scientific papers is akin to that person's absorptive capacity. When you start reading something, you come in with a host of prior knowledge: terms, phrases, principles, etc that you know and understand. The more of these things you have when reading relevant to the piece you're reading, the more quickly you can read, digest, critize, etc.
I've read this particular GFS paper a long time ago and this is a domain I can read through fairly rapidly (pro tip: read the abstract and conclusions first to make sure it's worth your time to read the meat of the paper given academic incentives to publish anything anymore).
I've worked with some medical professionals doing work on partial arthroplasty related techniques (adding 3D volume reconstructive techniques) and the paper took me forever to get through and contribute to because like you, every paragraph was me looking up medical terminology and trying to incorporate that into my baseline knowledge. My absorptive capacity was very low in that context.
In general, the more generalized scientific knowledge you have, the easier it is to pickup and read these papers quickly (if they've been written for a general scientific audience). If they're CS papers, clearly CS foundations help (theory, nomenclature, current and past popular trends, etc.).
Accept that you're going to be slow. Start with a paper you know will be worthwhile, something seminal in your field.
Get rid of all distractions, preferably by going to a different environment. Leave your phone at home or at the very least silence it and leave it in your bag. Print the paper out on dead trees, or otherwise display it on a medium that cannot display a web browser or other digital distractions.
Just start reading, deliberately reading every word. Underline or take notes in the margin if those might be your thing. When you get to something you don't understand, don't skip past it and figure you'll fill it in from context - read it again and make yourself figure out exactly what it means (exception: you can try figuring things out from context, but limit it to several sentences). You might have to look some things up to gain understanding, which un/fortunately today is via the web, but don't get distracted. If you're feeling overwhelmed you can take a break, but don't jump to another activity. Stick with it.
Eventually you will learn how to read dense things quicker, how to quickly figure out where something fits in a field, whether reading something in depth is worth it. But that will only come with experience.
Textbooks may be introductory in nature, or may be advanced and assume a lot of prerequisite knowledge.
If you are trying to learn about something new, you have to start with the basics.
If you are struggling and finding that the text makes no sense at all then ask yourself if you are diving too deep too fast.