\n
\n Paper a Week began as an experiment in personal accountability when I\n was a 3rd year PhD student. The idea is simple: read and take\n structured notes on one academic paper per week. Meeting that goal has\n helped me build a literature reading habit and organize my notes in a\n searchable, sortable, and shareable format. Wanting to share the\n benefits of this system with others, I built out Paper a Week into a\n standalone service capable of finding papers online, maintaining a\n reading list, writing rich notes with Markdown and LaTeX support, and\n providing habit-tracker statistics. Making an account is fast and\n free. Try it out!\n
\n\n
\n
Browse My Public Paper a Week Profile
\n \n\n
\n Explore the Code
\n \n A big part of my motivation for making{\" \"}\n \n Paper a Week\n {\" \"}\n was to learn modern web technologies including React, Redux, Express,\n Node.js, MongoDB, Docker, Google Cloud Run, Typescript, and more. That\n effort would have been much more painful if not for the expert guidance\n and patience of my mentor and identical twin brother,{\" \"}\n \n Arad\n \n . Given the nature of the project, I've made all of the code and commit\n history available to anybody interested.\n
\n\n \n \n
\n Paper a Week Github Repository\n
\n
\n Reflections
\n \n As of this writing, I had done 200 consecutive weekly reviews. My 200th\n review aligned with finishing my PhD, and I took the opportunity to take\n a break from weekly reviews and focus on other things. Here are my\n thoughts on Paper a Week after nearly 4 years of regular use:\n
\n \n - \n On Frequency: A lot of people might see 1 paper /\n week as unambitious, but I’ve found that it’s a great balance of\n regularity and sustainability. There were times in my PhD (like before\n my qualifying exam) where I was carefully reading many papers in a\n week, but there were also times — whole quarters sometimes! — where\n other things felt more urgent and I barely skimmed any papers, let\n alone read them carefully. 1 paper per week is a tangible target, and\n if I ever wanted to read more than that, I did.\n
\n\n - \n On Skimming: Taking notes on 1 paper / week doesn’t\n necessarily mean looking at 1 paper / week. For every paper I took\n notes on, there are 3-5 that I skim or stop reading halfway through.\n In fact, by choosing “The One” paper I’ll read that week, I usually\n end up skimming many alternatives and reckoning with whether a paper\n is actually relevant to my interests.\n
\n\n - \n On Old and New Literature: Reading a paper-a-week\n helped me do two things that I find important: First, it pushed me to\n actually scan the new literature on a weekly basis, instead of relying\n on Twitter to float a relevant article once a month. Second, in weeks\n where there was nothing relevant and new to read, it pushed me to find\n older papers that had flown under my radar.\n
\n\n - \n On a Personal Scientific Brand: Having a list of many\n papers that were of interest to me has helped defined my messy corner\n of scientific interests. Reflecting on all of the notes I’ve taken,\n the intersection of my interests in machine learning, vision, and\n cortical development is more apparent. After many weeks, Paper a Week\n provides an honest reflection of the work you find interesting,\n accessible, and important.\n
\n\n - \n On Memory: My memory for papers I’ve read isn’t\n great, and I’ve already used paperaweek.com to go back and remind\n myself of what my impressions were at the time I read a paper.\n
\n\n - \n On Notes as a Form of Reviewing: Taking critical\n notes on one paper per week has helped make me a better reviewer and\n critic of scientific work in journals, talks, and conferences. It's\n not a replacement for peer review, but it's still made me better at\n noticing details in papers.\n
\n
\n