| api_design | ||
| artificial_intelligence | ||
| audio_comp_sci | ||
| biocomputing | ||
| caching | ||
| clojure | ||
| comp_sci_fundamentals_and_history | ||
| computer_graphics | ||
| computer_vision | ||
| concurrency | ||
| cryptography | ||
| data_structures | ||
| datastores | ||
| design | ||
| digital_currency | ||
| distributed_systems | ||
| ethics | ||
| functional_progamming_winners | ||
| functional_reactive_programming | ||
| garbage_collection | ||
| historical/physics | ||
| information_retrieval | ||
| logic_and_programming | ||
| macros | ||
| networks | ||
| new_paradigms | ||
| operating_systems | ||
| pattern_matching | ||
| plt | ||
| processes | ||
| robotics | ||
| sports_analytics | ||
| .gitignore | ||
| README.md | ||
Papers We Love
Repository related to the following meetups:
- NYC - Papers We Love
- SF - Papers We Love too
- London - Papers We Love
- Saint Louis - Papers We Love
- Colorado - Papers We Love
Let us know if you are interested in starting a chapter!
Past Presentations
- Our latest presentation was led by Michael Bernstein on A Unified Theory of Garbage Collection
See the complete list of past presentations or check out our Youtube channel
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
- SciRate
- cat-v.org
- y-archive
- Bell System Technical Journal
- netlib
Please check out our wiki-page for links to blogs, books, exchanges that are worth a good read.
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
- Advice on reading academic papers
- How to read and understand a scientific paper
Contributing Guidelines
We have a few guidelines in place to keep the repo clean and easy to navigate. We recommend that you follow these conventions in your pull-request for a speedy merge. Note that every pull request we receive must have Two-Thumbs-Up minimum from PWL organizers/collaborators to be merged.
Follow the group's ethos
We want to help bring academic research closer to practitioners and we strive to:
- Keep the quality of papers listed high: Books, blogposts, and/or reference pdfs don't go through the same review process that academic papers do and we won't add them to this repo.
- Help people understand why a paper is important: We ask that you include with your commit an update to the directory README with a short justification of why you love this paper (for example: A paper might be interesting because it spawned a new domain, it was exceptionally well-written, or perhaps it was completely wrong about something.)
Respect content licenses
- We will only merge pull requests that contain research papers that allow digital distribution. Papers whose copyright prohibits redistribution will not be accepted; for example license 1 from the ACM digital library.
- We encourage papers that do not allow digital distribution to be added to a README in the appropriate subject's folder. For example, the distributed systems README.
Follow our naming convention
- 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.