| 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 | ||
| operating_systems | ||
| pattern_matching | ||
| plt | ||
| processes | ||
| robotics | ||
| sports_analytics | ||
| .gitignore | ||
| can-programming-be-liberated-from-the-von-neumann-style.pdf | ||
| millwheel-fault-tolerant-stream-processing-at-internet-scale.pdf | ||
| README.md | ||
Papers We Love
Repository related to the following meetups:
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
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. 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. 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.
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.
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.