PLDI Skills
A 12-skill depth pack for PLDI submissions: venue fit, HotCRP double-blind submission, author response, PACMPL camera-ready, Zenodo artifact evaluation with ACM badges, benchmark reproducibility, supplementary material, review process, writing style, related work, experiments, and workflow. Grounded in the PLDI 2026 CFP, pldi26.sigplan.org, PACMPL/ACM DL, and SIGPLAN policy pages checked on 2026-0
Skills in this plugin
11- ▌ Pldi Submission · brycewang-stanfordUse when auditing a PLDI submission for HotCRP readiness — the single annual November deadline, the 20-pages-of-text-excluding-bibliography cap in single-column acmsmall format, double-blind hygiene across tool names and repositories, dual-submission rules, and summary-rejection triggers before the cutoff.
- ▌ Pldi Experiments · brycewang-stanfordUse when designing or auditing a PLDI evaluation — choosing defensible benchmark suites and baseline compiler configurations, measuring runtime, compile time, and memory with warmup and variance discipline, running ablations that isolate the claimed mechanism, and scoping claims to the platforms measured.
- ▌ Pldi Camera Ready · brycewang-stanfordUse when turning an accepted PLDI paper into its PACMPL Issue PLDI article — de-anonymization, acmsmall journal formatting, ACM rights and open-access handling, delivering every author-response commitment, and coordinating the Zenodo artifact and June conference presentation.
- ▌ Pldi Related Work · brycewang-stanfordUse when positioning a PLDI paper against the SIGPLAN family and systems neighbors — stating technical deltas per cited line, covering the last few PLDI/POPL/OOPSLA/ICFP cycles, citing PACMPL-era papers in journal form, and verifying every venue attribution on dblp before it ships.
- ▌ Pldi Supplementary · brycewang-stanfordUse when deciding what accompanies a PLDI submission beyond the 20 text pages — full proofs, extended benchmark data, anonymized code — and how to keep every extra byte double-blind, optional for reviewers, and consistent with the main PDF under summary-rejection formatting rules.
- ▌ Pldi Writing Style · brycewang-stanfordUse when revising a PLDI draft for the venue's voice — design insight before tool name, mechanisms instead of adjectives, a running example that carries the semantics, honest limitation statements, and prose that fits the single-column acmsmall journal format without padding toward the page cap.
- ▌ Pldi Review Process · brycewang-stanfordUse when interpreting PLDI's review pipeline — double-blind HotCRP reviewing by a PL-implementor PC, the February author-response window, March notification, up-to-10% Distinguished Paper selection, and how post-acceptance artifact evaluation and PACMPL publication follow the decision.
- ▌ Pldi Author Response · brycewang-stanfordUse when drafting a PLDI author response inside the short February window — triaging reviewer objections about soundness, baselines, and benchmark validity, correcting factual errors with pointers into the submitted PDF, and committing to feasible revisions without promising new systems work.
- ▌ Pldi Reproducibility · brycewang-stanfordUse when hardening a PLDI paper's measurements against the SIGPLAN Empirical Evaluation Guidelines — warmup and steady-state discipline, variance and confidence reporting, principled benchmark choice, pinned toolchains, cross-platform validity, and a measurement log that survives artifact evaluation.
- ▌ Pldi Topic Selection · brycewang-stanfordUse when deciding whether a project is PLDI-shaped — implementation insight with benchmark-grade evidence — or better routed inside the PACMPL family to POPL, OOPSLA, or ICFP, or outward to ASPLOS, CGO, CAV, ICSE/FSE, or a systems venue, based on where the claim's evidence actually lives.
- ▌ Pldi Artifact Evaluation · brycewang-stanfordUse when packaging a PLDI artifact for the post-acceptance evaluation — earning the Functional, Reusable, and Available badges, archiving a DOI-stamped snapshot on Zenodo, containerizing toolchains and benchmark suites, and writing a README an evaluator can follow in a fresh VM.