Marketing & Growth

brycewang-stanford Skill

Use when positioning an EDBT submission against the data-management literature across SIGMOD, VLDB/PVLDB, ICDE, EDBT, the co-located ICDT, and the database journals (VLDBJ, TODS, TKDE), writing delta-first contrast rather than a citation catalog, and handling the 12-month EDBT resubmission ban, preprints, and prior-version overlap.

brycewang-stanford Skill

Use when positioning an ICCV paper against the literature, covering the intervening-cycle problem of citing a CVPR and an ECCV that happened since the last ICCV, concurrent-preprint etiquette around the March deadline, double-blind self-reference and the do-not-cite-your-repo rule, and venue-attribution hygiene across the vision big three.

brycewang-stanford Skill

Use when positioning an IEEE ICDE submission against the database canon and neighboring venues, running a reinvention audit across SIGMOD, VLDB, EDBT, and shipping systems, handling two-round concurrency, distinguishing engineering delta from genuine novelty, and covering both the literature and production systems an ICDE reviewer expects.

brycewang-stanford Skill

Use when positioning an ICDM (IEEE International Conference on Data Mining) paper's related work - lineage against prior ICDM editions and IEEE data-mining neighbors, the mechanism-contrast novelty sentence, avoiding KDD/SDM/CIKM/WSDM venue misattribution, and citing your own prior work in the third person so the section stays triple-blind-safe.

brycewang-stanford Skill

Use when positioning an ICDT (International Conference on Database Theory) paper against the database-theory literature — covering the ICDT/PODS lineage, finite model theory and complexity, delta-first positioning against the nearest prior theorem, honest treatment of overlapping bounds, and keeping self-citations anonymous under the since-2024 rule.

brycewang-stanford Skill

Use when positioning an ICLR paper against prior work, concurrent OpenReview submissions, arXiv papers, benchmark lineages, and adjacent learning-representation claims. Use when a reviewer cites a paper you missed, when a public comment disputes your novelty, or when separating "shares a component with" from "solves the same representation-learning problem" so the claim survives permanent public scrutiny.

brycewang-stanford Skill

Use when positioning an ICML submission against close ML literature, concurrent ICML submissions, recent public papers, workshop papers, ICLR/AISTATS/NeurIPS neighbors, and prior work under double-blind constraints.

brycewang-stanford Skill

Use when building or auditing the related-work section of an ICRA paper — covering the conference's own recent proceedings plus IROS, RSS, CoRL, RA-L, and T-RO lanes, handling arXiv-only robotics work, citing your own platform papers under ICRA's double-anonymous rules, and positioning against commercial systems.

brycewang-stanford Skill

Use when building the related-work and positioning sections of an ICSE research-track paper, covering the literature lanes SE reviewers check, searching ACM DL, IEEE Xplore and dblp across the flagship venues, staying current in fast-moving areas like LLM4SE, and keeping self-citations double-anonymous.

brycewang-stanford Skill

Use when positioning an IPSN-lineage submission against the sensor-networks and information-processing literature (IPSN, SenSys, MobiCom, MobiSys, INFOCOM, and signal-processing venues), writing delta-first contrast rather than a citation catalog, keeping self-citations double-blind, and handling concurrent, preprint, and prior-version overlap.

brycewang-stanford Skill

Use when positioning an IROS submission against robotics-systems literature across ICRA, IROS, RSS, CoRL, RA-L, and T-RO, covering the lanes embodied-systems reviewers check, concurrent arXiv work, prior-version overlap, IEEE Xplore archival status, and keeping self-citations anonymous under the double-anonymous cycle.

brycewang-stanford Skill

Use when positioning an ISCA submission against prior art — covering five decades of architecture literature across ACM DL, IEEE Xplore, and dblp, differentiating by mechanism rather than metric, handling self-citations and arXiv preprints under double-blind rules, and exploiting ISCA's unlimited reference pages.

brycewang-stanford Skill

Use when positioning an ITCS paper against the theory literature — writing the delta that proves the model/question is genuinely new, covering the right STOC/FOCS/SODA/CCC/TCC lanes, and staying honest under lightweight double-blind where the reference list is not anonymized.

brycewang-stanford Skill

Use when positioning an NDSS submission against prior literature — sweeping the security big four plus the specialist venues, writing precise deltas, verifying every citation against NDSS's open proceedings and dblp, and keeping self-reference double-blind.

brycewang-stanford Skill

Use when positioning an NSDI submission against the networked-systems literature — covering the NSDI/SIGCOMM/OSDI/SOSP lanes plus both accepted-paper cohorts of the current edition, verifying venues against dblp and open-access USENIX proceedings, and handling self-citations and concurrent submissions under double-blind rules.

brycewang-stanford Skill

Use when planning an OOPSLA campaign on the two-round clock — choosing October vs March entry, budgeting for Minor or Major Revision paths, mapping acceptance to the OOPSLA1 or OOPSLA2 PACMPL issue, scheduling artifact evaluation, and landing the SPLASH talk, with dates re-anchored to the live cycle.

brycewang-stanford Skill

Use when positioning an OSDI submission against prior systems literature — covering the OSDI/SOSP/NSDI/FAST/EuroSys/ATC lanes, verifying venues through USENIX's free open-access proceedings and dblp, and citing your own precursors without breaking the renamed-system anonymity rule.

brycewang-stanford Skill

Use 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.

brycewang-stanford Skill

Use when writing the related-work and positioning of an ACM PODC paper — covering the distributed-computing literature lanes (PODC/DISC/SPAA and the JACM / Distributed Computing journals), writing a model-and-bound-precise delta over prior results, distinguishing your model from neighboring ones, and keeping self-citation safe under lightweight double-blind review.

brycewang-stanford Skill

Use when positioning a POPL paper in the semantics, type-systems, and verification literature — stating per-line technical deltas against the nearest formal systems, covering the PACMPL family and LICS/CAV/CPP/TOPLAS neighbors, citing PACMPL-era papers in journal form, and dblp-verifying every classic before it is attributed to POPL.

brycewang-stanford Skill

Use when planning a SenSys campaign against the two-deadline calendar — deciding which deadline to target and which edition it feeds, backward-scheduling so energy campaigns and long-term deployments finish before freeze, budgeting time for the resubmission-with-revision path, and sequencing fit, building, writing, and submission.

brycewang-stanford Skill

Use when positioning an ACM SoCC submission against both the systems literature (OSDI, NSDI, EuroSys, ATC, SOSP, SoCC) and the data-management literature (SIGMOD, VLDB), writing delta-first contrast rather than a citation catalog, keeping self-citations dual-anonymous, and handling concurrent, preprint, and prior-version overlap.

brycewang-stanford Skill

Use when positioning a SODA (ACM-SIAM Symposium on Discrete Algorithms) paper in the algorithms literature — tracing bound lineages across SODA/STOC/FOCS/ESA/ICALP and journals, handling arXiv-first priority culture, citing conference versus journal versions correctly, and self-citation under lightweight double-blind rules.

brycewang-stanford Skill

Use when positioning a SOSP submission against the systems literature — the SOSP/OSDI lineage a PC expects you to know, structural comparison instead of citation listing, third-person self-citation under double-blind rules, and handling concurrent work across the now-annual systems deadline circuit.

brycewang-stanford Skill

Use when positioning a STOC (ACM Symposium on Theory of Computing) paper against the theory literature — tracing bound-improvement lineages, citing conference/journal/preprint version pairs correctly, handling concurrent arXiv and ECCC work, and keeping self-citation double-blind-safe.

brycewang-stanford Skill

Use when positioning a UIST submission against prior art — organizing by capability delta rather than paper lists, covering the technique lineage, toolkit ancestry, and commercial systems reviewers know, citing your own work in the third person, and verifying venue attribution through the ACM DL and dblp.

brycewang-stanford Skill

Use when positioning a PVLDB submission against prior literature, covering the deep database canon back to the 1980s VLDB proceedings, the SIGMOD/ICDE/CIDR neighborhood, concurrent work under rolling monthly deadlines, industrial and open-source systems as citable prior art, and overlap declarations for extended versions.

brycewang-stanford Skill

Use when positioning a paper against prior literature for WSDM - locating the work inside WSDM's own research lineages (click models, unbiased LTR, sequential recommendation, community detection), contrasting against SIGIR/KDD/WWW/CIKM/RecSys neighbors, venue-misattribution traps, and compressing the section for the tight page budget.

brycewang-stanford Skill

Use when positioning an AAMAS submission against multiagent, game-theory, and reinforcement-learning literature spread across AAMAS, AAAI, IJCAI, NeurIPS, ICML, EC, and JAAMAS, including arXiv and workshop versions, concurrent submissions, prior conference versions, and the cross-community citation coverage AAMAS reviewers expect.

brycewang-stanford Skill

Use when positioning an ACM CCS submission against the security big-four and specialist literature, including arXiv preprints, prior CCS/S&P/USENIX/NDSS papers, concurrent disclosures, CVE and advisory records, and the attack-and-defense lineage that a SIGSAC program committee expects to see credited.

brycewang-stanford Skill

Use when positioning an EMNLP submission inside NLP's fast-moving literature — covering ACL Anthology lineages and arXiv concurrency, citing Findings and workshop papers correctly, tracing dataset and benchmark ancestry, verifying every reference resolves under the hallucinated-citation policy, and keeping self-citation double-blind.

brycewang-stanford Skill

Use when planning a EuroSys campaign end to end — choosing between the spring and fall gates of an edition, backward-scheduling system building and evaluation from the abstract deadline, handling the notification-to-revision-to-resubmission pipeline, and landing camera-ready, artifacts, and April travel for the conference.

brycewang-stanford Skill

Use when positioning an ACM FAccT submission across its many disciplinary lanes — algorithmic fairness/ML, HCI, law and policy, STS and critical theory, and prior FAccT/FAT* proceedings — writing delta-first contrast that a mixed reviewer pool will accept, citing borrowed constructs to their real origin, keeping self-citations mutually anonymous, and declaring overlap with workshops, preprints, and prior versions.

brycewang-stanford Skill

Use when writing the related-work and positioning of an ICALP (EATCS) theory paper — comparing against the best known bounds in the TCS literature, crediting the right prior venues (STOC/FOCS/SODA/LICS/CCC and TCS journals), stating the delta precisely, and keeping self-citations third-person under lightweight double-blind.

brycewang-stanford Skill

Use when positioning an IEEE ICSME submission against the software-maintenance and evolution literature across ICSME, SANER, MSR, ICPC, SCAM, ICSE/FSE, and the SE journals (TSE, EMSE), writing delta-first contrast rather than a citation catalog, keeping self-citations double-anonymous, and handling replication overlap and prior-version eligibility.

brycewang-stanford Skill

Use when positioning an IJCAI or IJCAI-ECAI submission against archival AI literature, arXiv preprints, workshop papers, prior rejected versions, dual-submission rules, shortened prior versions, and resubmission-information requirements.