mirror of
https://github.com/papers-we-love/papers-we-love.git
synced 2024-10-27 20:34:20 +00:00
api_design | ||
artificial_intelligence | ||
audio_comp_sci | ||
caching | ||
clojure | ||
comp_sci_fundamentals_and_history | ||
concurrency | ||
data_structures | ||
datastores | ||
design | ||
digital_currency | ||
distributed_systems | ||
ethics | ||
functional_progamming_winners | ||
functional_reactive_programming | ||
garbage_collection | ||
logic_and_programming | ||
macros | ||
networks | ||
new_paradigms | ||
pattern_matching | ||
plt | ||
processes | ||
sports-analytics | ||
.gitignore | ||
can-programming-be-liberated-from-the-von-neumann-style.pdf | ||
dynamo-amazons-highly-available-key-value-store.pdf | ||
millwheel-fault-tolerant-stream-processing-at-internet-scale.pdf | ||
out-of-the-tar-pit.pdf | ||
README.md | ||
reflections-on-trusting-trust.pdf |
Papers We Love
Repository related to the following meetups:
Let us know if you are interested in starting a chapter!
Info
We're looking for pull requests related to papers we should add, better organization of the papers we do have, and/or links to other paper-repos we should point to.
Other Good Places to Find Papers
- Best Paper Awards in Computer Science
- Google Scholar (choose a subcategory)
- Microsoft
- Vijay D'Silva
- Functional Programming Books Review
- MIT's Distributed System's Reading Group
- arXiv Paper Repository
How To Read a Paper
Reading a paper is not the same as reading a blogpost or a novel. Here are a few handy resources to help you get started.
- [How to read an academic article] (http://organizationsandmarkets.com/2010/08/31/how-to-read-an-academic-article/)
- [Advice on reading academic papers] (http://www4.ncsu.edu/~akmassey/posts/2012-02-15-advice-on-reading-academic-papers.html)
- [How to read and understand a scientific paper] (http://violentmetaphors.com/2013/08/25/how-to-read-and-understand-a-scientific-paper-2/)
Contributing Guidelines
We have a few guidelines in place to keep the repo clean and easy to navigate. Follow these conventions in your pull-request for a speedy merge.
- Directory names are undercased and separated by underscores (example:
artificial_intelligence
) - Paper names are undercased and separated by dashes (example:
out-of-the-tar-pit.pdf
). Use the full title when possible.
Papers We Love Presentations
- Check out our Youtube channel
- Michael Bernstein on A Unified Theory of Garbage Collection