Links to the papers: https://docs.google.com/spreadsheets/d/1wS6O7-ZoFL7Cfjgt-kdh...
I've been slowly reading through them - some easier than others. (Some I've pretty much skipped - way too long for my interests).
I've found that the original papers are always super dense and the material has usually evolved to be more explainable, especially when someone has put in the time to compile it as part of a course.
I have not finished it yet, just went through a few chapter, but I can definitely recommend it!
Yep. I didn't realize so much has changed with the rest of the site There was a bit of slowdown I presume in mid-2010s where the table felt a tad behind schedule. I did think of personally writing you an email to help in updating if necessary. In fact, I secretly wanted to just mirror your publication page - but stealing someone's thunder wasn't my ballgame :)
Question though, have you got a process for reading individual papers? In college my old CS professors insisted on reading the abstract, then the conclusions, then the references, and then the rest of it.
Summary at - https://derekchia.com/how-to-read-a-research-paper-3-pass-ap...
More Advice from S.Keshav - https://svr-sk818-web.cl.cam.ac.uk/keshav/wiki/index.php/Adv...
I have heard that advice before, but I generally disagree. Unless you are doing a literature search, reading the references is a waste of time. And most conclusions aren't really worth reading either. They typically read as though the author has completely exhausted themselves by writing the rest of the paper, and simply restart the last paragraph of the introduction in new words.
If you are trying to get up to speed on a new field, a good introduction can really help with you reference search.
Part of "how to read a paper" depends on what you are trying to do. If it's a seminal paper that are are just going to read, that is a very different thing from reading a paper in search of a solution (or trying to figure out of your idea is novel).
In this second case, your main task is to decide if the paper is even worth reading. IMO, this takes a lot practice. Fully reading a paper to the extent you really understand it can be extremely time consuming. It's important to be willing to throw out the paper if at any point (no matter how much time you've put into it) it becomes clear it doesn't work for you.
I will generally skim the abstract and/or the last two paragraphs (or so) of the introduction. If it still sounds promising I look through the next section or two, which are usually some kind of "problem setup" and "proposed solution scheme". I skip things I don't immediately understand. If my interest is still piqued, I look for the results section where the plots are (if it's a practical paper). If I'm still interested, I go back to Section II and start reading more carefully. I'll spend more time with tricky math, but not too much. Save staring at the same four equations for two hours for at least the third pass.
Oh, and if a paper is tricky (for me) and seems worth my time, printing it out single sided and laying the pages out side by side on my desk can be really helpful.
Also, do you think ACM opening their archives will have a high impact on which ones you recommend in the future?
ACM archives -- not really, I haven't added any new conferences because it makes each year even more work to update. And I find that nearly all CS papers are accessible through various sources that you can find in Google Scholar or Semantic Scholar (e.g. author homepages, course websites, arXiv, etc.).
This collection is great - thanks so much for your effort!
https://jeffhuang.com/best_paper_awards/
These are papers that were deemed "best papers" in that year, though obviously may not have turned out to be as influential in retrospect, i.e. they're likely not the papers we consider "best" when looking back today.