← LibraryBlog · AI

Jakub and Szymon

Sam Altman
✓ Source-grounded

The breakthrough of modern AI is a story of human ingenuity, driven by the relentless combination of research and engineering to solve problems deemed impossible.

Read the original

In one sentence

The rapid advancement of AI is not a magic trick of technology, but a triumph of human ingenuity where research and engineering are combined to solve "impossible" problems.

Why read this (and who it's for)

This piece strips away the "magic" of the AI interface to reveal the grueling human effort required to build it. It is for anyone who wants to understand the operational reality of high-stakes innovation—specifically how to combine research and engineering to break through conventional wisdom. After reading, you will be able to identify the "hidden" engineering required for your own complex projects and recognize the importance of complementary partnerships.

The big idea

AI is often presented as a "black box" of magic, but Altman argues that behind the "blinking circle" of a user interface lies a story of human progress and ingenuity. The core of this progress is the ability to take on problems that experts thought were impossible on this timeframe and build the infrastructure necessary to make those breakthroughs happen.

The logic of the book rests on the synergy between Research and Engineering. While research asks "what is possible?", engineering asks "how do we scale it?" Altman argues that the most significant breakthroughs—like the ones led by Jakub Pachocki and Szymon Sidor—happen when these two disciplines are fused to challenge conventional wisdom and build the foundations for scientific discovery.

Key ideas

The Hidden Labor of Progress

Challenging Conventional Wisdom

The Research-Engineering Synthesis

Infrastructure as a Catalyst

Complementary Partnership

Frameworks & tools

The text describes a method of Research-Engineering Synthesis for solving "impossible" problems. You can use this approach to tackle your own complex projects:

The Research-Engineering Synthesis Method

  1. Identify the "Impossible" Problem: Find a challenge where the "conventional wisdom" says it cannot be solved or scaled.
  2. Establish a Baseline: Instead of trying to solve the problem immediately, scale the current baseline (e.g., RL) to see exactly where it breaks.
  3. Build the Infrastructure: Create the underlying systems and tools that will allow for scientific discovery and experimentation.
  4. Combine Research and Engineering: Pair a research-heavy approach (the "why") with an engineering-heavy approach (the "how") to iterate on the solution.

Memorable examples & stories

The RL Scaling Experiment Pachocki and Sidor took Reinforcement Learning (RL) and scaled it up as a baseline specifically to see where it broke, despite the prevailing belief that it wouldn't scale. Lesson: To find the limit of a technology, you must intentionally push it until it fails.

The Infrastructure for Discovery The duo built the core infrastructure that served as the foundation for many of OpenAI's scientific discoveries. Lesson: True innovation often requires building the "pipes" before the "water" can flow.

The Reasoning Breakthroughs Pachocki and Sidor, working with Ilya and Lukasz, drove the initial ideas that led to the reasoning breakthroughs in AI. Lesson: Breakthroughs are the result of collaborative, multi-person efforts to explore new paradigms.

Key quotes

"AI has gotten remarkably better in recent years; ChatGPT can do amazing things that we take for granted." This reminds us that progress is often hidden behind a seamless user experience.

"There are two people I'd like to mention that OpenAI would not be OpenAI without: Jakub Pachocki and Szymon Sidor." This highlights the importance of key individuals in the history of technology.

"OpenAI has not yet thrown a problem at them they have not been able to solve." (Paraphrased) This illustrates the power of a perfect research-engineering partnership.

How to apply it

This week

Ongoing

Common pitfalls

Connects to

The provided material does not cover any related books or external ideas.

If you remember only three things

Internalize it

Fidelity note

I have a high level of confidence in this summary as it is derived strictly from the provided blog post. The summary captures the specific roles of Jakub Pachocki and Szymon Sidor, the importance of the Research-Engineering synthesis, and the specific examples of RL scaling and infrastructure building. The "Connects to" section is empty as per the instructions to not invent content.

Keep going — related reads

More from Sam Altman