Hey friends, Over the past 18 months, the Latent Space Paper Club has had an unbroken streak of hosting paper club every single week. That’s at least 80 papers, and likely more, when we consider weeks where we cover related papers (e.g., LoRA + QLoRA). Together, we’ve pre-read and discuss a paper weekly, covering the fundamentals such as:
If you’re looking to get started, here’s a year’s worth of notable papers. This has equipped us with the foundation to understand how these techniques and models work, build systems and applications on top of them, and apply them at work and personal projects. But it’s not just about technical knowledge. We’ve also learned from practitioners sharing their insider know-how, built friendships at in-person meetups, and grown a community of learners and builders. We’d like you to benefit from this too. That’s why we wrote this guide: To help you start your own paper club and learn—together—with your peers. Also see the Swyx/Latent Space version that includes (i) advice on paper curation, (ii) video walkthrough of a 3-paper pre-reading + slide prep, (iii) recordings of the Llama 3.1 and Molmo paper club, and more. I appreciate you receiving this, but if you want to stop, simply unsubscribe. P.S., My friend Jason's AI Consultant Accelerator—Dec 9th to 13th—is filling up fast. And it gets you a discount for his RAG course if you take it later! Use EY20 for 20% off! • • • 👉 Read in browser for best experience (web version has extras & images) 👈
How the Latent Space Paper Club got started ~18 months ago What happens at paper club (doesn’t just stay at PC)Same time, every week. Every Wednesday, we gather for an hour over lunch (12pm PST) to discuss a pre-selected paper. Sticking to the same time every week makes it easier to remember and attend. Also, a weekly cadence helps with building the habit. Pre-reading. Pre-reading the paper helps you get the most out of the session. I usually pre-read over the weekend, for about an hour. This helps me identify what I don’t understand so I know what to clarify during the session. I’m also better equipped to share insights and help others understand the material. From experience, skipping the pre-read reduces the value I get from the discussion by ~80% or more.
Yes, please pre-read the paper Facilitating. Each week, a volunteer guides the group through the paper, covering the motivation, related literature, methodology, results, etc. This usually takes around 45 minutes, with pauses after each section for quick questions. In the last 15 minutes, we have free-form discussion and discuss the paper’s implications, connect it to other work, and/or consider how to apply the ideas to our work and the broader industry. Some facilitators prepare simple slides highlighting key charts and takeaways, but this isn’t mandatory. Personally, I’m too lazy to create slides and just screen-share my annotated paper with highlights and notes. How to run a paper club (with minimal effort)Selecting papers. The facilitator gets to pick whatever paper they want to discuss, within the overall theme. While our paper club’s focus is language modeling, we occasionally explore key papers from other domains like vision (e.g., CLIP, ViT, LCMs), audio (e.g., Whisper, Moshi), and RL (e.g., DPO, PPO). TIP: At the start of each session, ask for volunteers to facilitate next week’s paper. This helps you avoid a last-minute scramble to find a facilitator and paper. Scheduling. We use Luma for event management but it lacks support for recurring events. We’ve also used Discord events but it’s only visible to folks in the Discord. If you have a better solution, please share! Hosting. We host sessions on a paid Zoom account (thanks Swyx!) We’ve also tried Discord Stages for a bit but had issues with screen sharing and viewing. Recordings. We record the paper facilitation (via Zoom), but not the Q&A. By not recording the Q&A, we hope to encourage folks to share their experience and ghost knowledge (which is sometimes based on what they do on the job). This also incentivizes live attendance and participation in the Q&A which, IMHO, is the main benefit of paper club. Community. Our paper club started as a small group that was committed to studying a key paper each week, and in the process, level up on language modeling together. Over time, we’ve grown into a core group of facilitators and regulars (Swyx, Vibhu, Eugene Cheah, Amgad, Eric, RJ, etc). Including myself, this critical mass lets us rotate amongst ourselves every two months or so, though new volunteers are always welcome! Inviting authors. Occasionally, we invite authors to share their work and have had the pleasure of hosting Llama, Matryoshka Embeddings, Writing in the Margins, TimeGPT, etc. We’ve also invited Shreya and Nathan to join us while we discuss their papers. Having the authors join paper club allows us to clarify our questions with them directly, and lets the authors share behind-the-scenes insights. For example, we learned from Nathan why Molmo has such a heavy emphasis on analog clocks. How to read a paper (in an hour)Reading papers. If you find reading academic papers challenging, you’re not alone. The three-pass approach (video) has served me well:
Most of the time, unless you’re trying to replicate the paper, two passes will suffice. Nonetheless, for paper club, I tend to go into the details on methodology and results. Here’s my walkthrough of applying the three-pass approach. Tools. Zotero makes it convenient to save papers to your library. It also has built-in markup tools to highlight and annotate papers. And if you come across unfamiliar terms or inscrutable math equations, take a screenshot and ask Claude to explain! How to facilitate a paper (even if it’s your first time)Topics. When guiding the group through the paper, focus on these key aspects.
Format. Most facilitators simply walk through the PDF with their highlights and notes. Others create simple slides, including key graphs and tables to focus attention. There’s no hard and fast rule—just do what suits you best as facilitator. • • • Participating in a weekly paper club means covering ~50 papers a year. With just two hours per week—one hour of pre-reading and one hour of discussion—you’ll spend only ~100 hours (4 days) a year. Yet, this minimal effort likely places you in the top 5% of AI engineers and the top 0.1% of the world population in terms of AI knowledge. So, what are you waiting for? Start your own paper club, or see you at Latent Space! |
I build ML, RecSys, and LLM systems that serve customers at scale, and write about what I learn along the way. Join 7,500+ subscribers!
Hey friends, To better understand MCPs and agentic workflows, I built a news agent to help me generate a daily news summary. It’s built on Amazon Q CLI and MCP. The former provides the agentic framework and the latter provides news feeds via tools. It also uses tmux to spawn and display each sub-agent’s work. P.S. If you’re interested in topics like this, my friends Ben and Swyx are organizing the AI Engineer World’s Fair in San Francisco on 3rd - 5th June. Come talk to builders sharing their...
Hey friends, I've seen many teams misunderstand what it means to build and apply product evals and wrote this piece to address it. I hope it clarifies that evals aren't a one and done artifact, but a disciplined process. Do you agree or disagree? Please reply and let me know! P.S., In May, my friends Hamel Husain and Shreya Shankar are teaching an exclusive 4-week course on "AI Evals for Engineers & PMs". They've generously provided a special 40% discount link 🤫—but hurry, limited spots...
Hey friends, Every month or so, I receive questions about my writing: “How did you get started?” “Why do you write?” “Who do you write for?” “What’s your writing process?” I’ve procrastinated on writing this FAQ because, honestly, who cares about my writing process? But after answering the same questions again and again, I realized it’d be helpful to consolidate my responses somewhere. At the very least, it’ll save me from repeating myself. If you’re thinking about writing online but aren’t...