Diogo Almeida, Co-author of GPT-4 and RLHF: Current AI is Designed to Please Humans, Not Work Autonomously
Diogo Almeida is a co-author of the OpenAI GPT-4, ChatGPT, and RLHF/InstructGPT papers. Speaking at the AI Engineer conference, he argued that nearly all large language models today are trained by optimizing for human preferences, making them adept at pleasing humans but incapable of true automation.
ImportanceStructuralEvidenceE3 inspectableWrite-upStandard
AI can solve unsolved mathematical problems yet struggles with seemingly simple decisions in customer service. This contrast confuses many: if models are so smart, why do we still need to hire people for tasks that appear more trivial?
At the AI Engineer conference, Diogo Almeida offered a structural explanation. He is a co-author of OpenAI's GPT-4, ChatGPT, and the RLHF/InstructGPT papers; his team essentially coined the concept of "post-training." He noted that he is one of the few insiders at OpenAI who publicly critiques ChatGPT, not out of dislike for the product, but because he believes much of what is happening in the AI field today traces back to specific design decisions made when developing the algorithms behind ChatGPT.
His core judgment is that today's AI is designed for assistance through the optimization of human preferences; it cannot achieve automation. This is not a matter of insufficient capability, but of the objective function. The essence of RLHF is a two-step process: collecting human preferences and optimizing for them. The goal of this loop is to satisfy humans, not to enable software to run autonomously.
Consequently, overpromising is a feature, not a bug. Almeida explained that there is an asymmetry in reward models similar to Generative Adversarial Networks (GANs): it encourages models to discard nuance and appear confident, as reward models easily detect and penalize uncertainty. Hallucinations, in his view, are an inherent byproduct of optimizing for human preferences. When uncertain, the model chooses to please human preferences—which makes sense if you are the user in the loop, as the endgame for all RLHF models is to optimize engagement.