Skill UI

This skill guides authors writing about programming languages, software systems, and PL applications on how to assess if their manuscript is a suitable fit for the OOPSLA conference. It provides strategies for reframing papers, defining the required evidence (empirical, formal, or tool-based), and positioning the work against established CS research standards for top-tier systems conferences.

This guide details the rigorous, multi-phase artifact evaluation process for research papers submitted to OOPSLA. It covers best practices for creating robust, reproducible, and reusable software artifacts, aiming to achieve Functional, Reusable, and Available badges. Learn how to structure your repository, map claims explicitly, and pass the 'kick-the-tires' dry run, treating every evaluator as a hostile fresh VM.

This guide provides a structured approach for writing high-stakes author responses to academic paper reviews (like those in OOPSLA). It teaches authors how to move beyond simple rebuttals by framing every concern as an argument supporting a desired outcome (Accept, Minor Revision, Major Revision, or Reject). Focus areas include quantifying feasibility, structuring the argument for committee skimming, and strategically shaping the scope of required revisions.

A comprehensive guide for authors transitioning an accepted OOPSLA conference paper into a journal article for PACMPL. It details crucial steps including formatting changes, de-anonymization, updating Data-Availability Statements, managing author identities (ORCID), handling ACM open-access rights, and preparing for the associated presentation talk (SPLASH).

This guide provides a framework for designing and auditing the experimental rigor of academic papers, particularly in systems and programming languages. It emphasizes the crucial link between a claim type (e.g., 'Faster') and the required evidence type (e.g., benchmarks, user studies, formal proofs). Learn how to establish robust baselines, define clear workload rules, size experiments for conference cycles, and ensure statistical compliance for maximum impact.

A comprehensive guide for authors preparing the 'Related Work' section for top-tier academic conferences focused on programming languages, such as OOPSLA. It details rigorous citation standards (PACMPL journal format), mandates comprehensive venue coverage (POPL, PLDI, ICFP, etc.), and emphasizes identifying precise technical differences ('deltas') between the proposed work and existing literature, moving beyond mere inventory listing.

This guide provides comprehensive best practices for achieving scientific reproducibility in systems and programming language papers, following stringent SIGPLAN guidelines. It details the necessary rigor for documenting hardware, managing complex runtime measurements (like JIT warmup and variance), and maintaining a detailed, machine-readable provenance ledger and data-availability statement.

A comprehensive guide detailing the multi-stage, double-anonymous review process used at major academic conferences like OOPSLA. It explains the four possible outcomes (Accept, Minor/Major Revision, Reject), the mechanics of 'round-hopping' between submission volumes, and provides strategic advice on how to write author responses and manage revision expectations to maximize publication chances.

A comprehensive guide detailing the strategic and technical requirements for submitting research papers to major conferences like OOPSLA. It covers critical steps such as selecting the correct submission round, adhering to strict formatting rules (e.g., page limits), proactively maintaining double-anonymity, properly filing Data-Availability Statements, and managing complex revision or concurrent submissions to maximize acceptance chances.

This comprehensive guide assists reviewers and authors in determining the most appropriate venue for programming language research within the SIGPLAN community. It provides a detailed 'center-of-mass' test, helping categorize contributions based on whether they emphasize metatheory (POPL), performance engineering (PLDI), functional techniques (ICFCP), or the broad design scope characteristic of OOPSLA. It guides the decision-making process for academic submissions.

This comprehensive guide outlines the entire lifecycle of submitting and revising academic papers for major conferences like OOPSLA. It details strategic decisions, such as choosing between October or March submission rounds, managing the state machine (Accept, Minor, Major Revision, Reject), budgeting time for necessary revisions, and planning post-publication artifacts and talks. Essential for academic research teams.

A comprehensive guide for authors aiming to submit top-tier technical papers (like those for OOPSLA). It teaches how to transform descriptive drafts into highly verifiable, structured academic arguments. Focus areas include developing running examples, articulating falsifiable claims, optimizing article pacing, and anticipating reviewer challenges to maximize the chances of acceptance.