Skip to content

Seminar Guide

Seminars turn readings into technical argument rather than summaries.

Expected paper discussion structure

  1. What problem is being solved and why does it matter?
  2. What is the unit of analysis: class, pattern instance, commit, project, developer task?
  3. What representation and assumptions are used?
  4. What is the baseline?
  5. What data or oracle is used?
  6. What result most strongly supports the claim?
  7. What failure case most strongly weakens it?
  8. What would you replicate or change?

Discussion rule

Every critique should distinguish:

  • methodological flaw;
  • scope limitation;
  • reasonable design choice with trade-offs;
  • open research question.