Skip to main content
Original: Dan Shipper (Every) · 19/12/2025

​
Summary

Every session is onboarding this new coworker [anew]. Four OpenAI engineers built the Android version of the image generation app Sora in 28 days. Naturally, they built it using Codex,

​
Key Insights

“Every session is onboarding this new coworker [anew].” — Describes the approach of treating Codex as a coworker rather than a mere tool.
“Onboard your AI like a new hire.” — Highlights the importance of interactive and gradual introduction of AI into the workflow.
“It doesn’t get easier—you go faster.” — Reflects on how AI tools change the dynamics of coding, emphasizing speed over simplicity.

​
Topics

​
Full Article

# OpenAI Gave Us a Glimpse Into Their AI Coding Playbook
Author: Dan Shipper (Every)
Published: 2025-12-19
Source: https://every.to/source-code/openai-gave-us-a-glimpse-into-their-ai-coding-playbook
Midjourney/Every illustration. Four OpenAI engineers built the Android version of the image generation app Sora in 28 days. Naturally, they built it using Codex, their AI coding agent. Partway through that sprint, one of those engineers, RJ Marsan, shattered his wrist in a bike race, leaving him unable to type. So he cobbled together a speech-to-text system and started talking to Codex instead of typing commands himself. That forced constraint—having to tell the computer what to do rather than execute the instructions via his keyboard—taught him something the rest of the team eventually adopted: Treating Codex like a new coworker you’re onboarding delivers stronger results than treating it like a tool you’re configuring (Codex doesn’t remember previous conversations automatically). “Every session is onboarding this new coworker [anew].” Marsan and Alexander Embiricos, who leads the Codex product team, joined us for Every’s first-ever Codex Camp to share this and other insights learned building Sora with Codex and how generally to think about working with AI. Here’s what we learned.

​
Key takeaways

  1. Onboard your AI like a new hire. Start with quick, interactive prompts. Build trust. Let it learn your preferences. Then delegate longer tasks.
  2. Don’t overload context. If you’d overwhelm a coworker with 6,000 facts about your codebase, you’ll overwhelm the AI too. Give it what it needs for the task at hand.
  3. Narrow beats broad. An agent with one focused job outperforms a generalist trying to catch everything.
  4. It doesn’t get easier—you go faster. AI tools shift the bottleneck; they don’t eliminate it. Architecture and code review become more important, not less.

​
How to think about working with AI

Building Codex changed how the OpenAI team thinks about AI agents…

​
Key Takeaways

​
Notable Quotes

Every session is onboarding this new coworker [anew].
Context: Describes the approach of treating Codex as a coworker rather than a mere tool.
Onboard your AI like a new hire.
Context: Highlights the importance of interactive and gradual introduction of AI into the workflow.
It doesn’t get easier—you go faster.
Context: Reflects on how AI tools change the dynamics of coding, emphasizing speed over simplicity.
  • [[topics/pair-programming]]
  • [[topics/ai-agents]]
  • [[topics/prompt-engineering]]

Introducing the Codex app

Simon Willison · explanation · 80% similar

How Every Is Harnessing the World-changing Shift of Opus 4.5

Dan Shipper (Every) · explanation · 78% similar

My AI Had Already Fixed the Code Before I Saw It

Dan Shipper (Every) · explanation · 76% similar
Originally published at https://every.to/source-code/openai-gave-us-a-glimpse-into-their-ai-coding-playbook.