tayllan

Exactly my thoughts when I first saw the repo, it's just too much for me to be able to decide. A better approach I recommend is starting with an easy and interesting paper, reading it even if not in full, and then going through the references, which are sure to have some more interesting papers to read.

Aho-Corasick "Efficient String Matching: An Aid to Bibliographic Search", or Bentley-McIlroy "Data Compression Using Long Common Strings" are 2 such good places to start.

What worked for me was starting with some simple one, a bit technical, but not over the top. I think the first paper I really read, and this was a couple months ago, was Facebook's "Gorilla: A Fast, Scalable, In-Memory Time Series Database"[0]

After that, I started to write 1-3 paragraph summaries to myself, so that I could always come back to the main takeaways, because I know I'll forget it after 1 week.

And then, last week I created a Twitter account where I post these opinionated summaries [1]

[0] https://www.vldb.org/pvldb/vol8/p1816-teller.pdf

[1] https://twitter.com/paper_takeaways

I recommend https://www.amazon.com.br/Debugging-Indispensable-Software-H...

It has concrete points to focus when debugging and a bunch of examples for each. And it's easy to read as an introduction to the subject.