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

推荐订阅源

S
Schneier on Security
有赞技术团队
有赞技术团队
T
The Blog of Author Tim Ferriss
F
Fortinet All Blogs
D
DataBreaches.Net
F
Full Disclosure
腾讯CDC
博客园 - 【当耐特】
MyScale Blog
MyScale Blog
Stack Overflow Blog
Stack Overflow Blog
小众软件
小众软件
Hugging Face - Blog
Hugging Face - Blog
Last Week in AI
Last Week in AI
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
爱范儿
爱范儿
The GitHub Blog
The GitHub Blog
Engineering at Meta
Engineering at Meta
大猫的无限游戏
大猫的无限游戏
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
S
SegmentFault 最新的问题
The Register - Security
The Register - Security
WordPress大学
WordPress大学
博客园 - 聂微东
雷峰网
雷峰网
J
Java Code Geeks
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
P
Privacy International News Feed
酷 壳 – CoolShell
酷 壳 – CoolShell
A
Arctic Wolf
Scott Helme
Scott Helme
C
Cyber Attacks, Cyber Crime and Cyber Security
T
Tor Project blog
博客园 - 三生石上(FineUI控件)
Know Your Adversary
Know Your Adversary
AWS News Blog
AWS News Blog
G
Google Developers Blog
www.infosecurity-magazine.com
www.infosecurity-magazine.com
C
CERT Recently Published Vulnerability Notes
O
OpenAI News
Project Zero
Project Zero
K
KPMG report finds enterprise disconnect between AI and its ROI | CIO
Application and Cybersecurity Blog
Application and Cybersecurity Blog
云风的 BLOG
云风的 BLOG
N
News and Events Feed by Topic
MongoDB | Blog
MongoDB | Blog
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
Microsoft Security Blog
Microsoft Security Blog
Cisco Talos Blog
Cisco Talos Blog
P
Palo Alto Networks Blog
Schneier on Security
Schneier on Security

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 🐶