惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

W
WeLiveSecurity
The GitHub Blog
The GitHub Blog
Engineering at Meta
Engineering at Meta
Microsoft Azure Blog
Microsoft Azure Blog
The Register - Security
The Register - Security
Stack Overflow Blog
Stack Overflow Blog
博客园 - 三生石上(FineUI控件)
T
Threat Research - Cisco Blogs
S
SegmentFault 最新的问题
V2EX - 技术
V2EX - 技术
Hacker News: Ask HN
Hacker News: Ask HN
K
KPMG report finds enterprise disconnect between AI and its ROI | CIO
P
Proofpoint News Feed
J
Java Code Geeks
Microsoft Security Blog
Microsoft Security Blog
M
MIT News - Artificial intelligence
AI
AI
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
P
Proofpoint News Feed
Hacker News - Newest:
Hacker News - Newest: "LLM"
B
Blog
N
News and Events Feed by Topic
N
News | PayPal Newsroom
Google DeepMind News
Google DeepMind News
酷 壳 – CoolShell
酷 壳 – CoolShell
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
WordPress大学
WordPress大学
C
Cybersecurity and Infrastructure Security Agency CISA
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
博客园 - 【当耐特】
U
Unit 42
腾讯CDC
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
The Cloudflare Blog
H
Help Net Security
Recent Announcements
Recent Announcements
P
Privacy & Cybersecurity Law Blog
IT之家
IT之家
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
Security Archives - TechRepublic
Security Archives - TechRepublic
L
LINUX DO - 热门话题
Martin Fowler
Martin Fowler
MongoDB | Blog
MongoDB | Blog
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
H
Heimdal Security Blog
博客园 - 聂微东
S
Securelist
大猫的无限游戏
大猫的无限游戏
Cloudbric
Cloudbric
Cisco Talos Blog
Cisco Talos Blog

Haoxiang’s Blog

May. 2nd, 2026 Feb. 19, 2026 Feb. 12, 2026 Jan. 7 2026 My Coding Experience with AI
Jan. 12, 2026
Haoxiang Li Published 2026/01/12 · 2026-01-13 · via Haoxiang’s Blog

Some random (and mildly fun) thoughts while helping with a recent conference:

Recent major AI conferences (NeurIPS, ICLR, CVPR) have all suffered from the issues of overwhelming submission volumes, and the reviewer pool inevitably expanded. The Organizers have then found themselves battling against LLM-generated reviews. ACs were asked to identify such irresponsible reviewers, authors were out-raged, and stronger rules were introduced to penalize them.

I started wondering: instead of battling against LLMs, can we instead fully embrace the idea of using LLMs to review papers? Can we spend our efforts on building a capable LLM reviewer, rather than continuing to review everything ourselves?

Imagine all the benefits of having a capable LLM review submissions. The workload would no longer be a concern. Turnaround time would be much shorter. Bias could be largely reduced. Of course, there would be issues to be addressed. But tackling those challenges feels far more interesting than reviewing papers one by one.

We should ask the team of SACs, ACs, and our top reviewers to spend time collectively building a capable LLM reviewer for the conference.

Major AI conferences have 100+ SACs and 1000+ ACs, all of them are top talents. If they are already contributing their time to the conference (for free!), we should make the best possible use of that effort!

Reviewing for a given year is largely a one-off effort. The know-how is not retained in a way that could be leveraged without relying on these experts. If, instead, we organized them each year to spend time improving the LLM reviewer, we would be building something long-lasting and potentially increasingly capable over time.

The exact implementation is not straightforward. As a baseline, we could ask each committee member to contribute an agent or model that represents their reviewing style and preferences. They could tune the model as much as they like to better reflect their opinions. The rebuttal process could provide valuable data for RLHF. We could also ask big tech to sponsor the GPU costs for this effort.

— arising from some involuntary procrastination during the review process 🐶