This episode explores why knowledge workers should replace traditional documents like slide decks and PDFs with interactive websites or web apps, especially using AI tools like OpenAI's Codex. The host outlines over a dozen problems with static files—such as versioning chaos, poor navigation, and lack of observability—and provides 18 concrete examples of artifacts that work better as websites, from strategy memos to client portals.
Summarized by Podsumo
Websites solve the 'update versioning curse' by providing a single canonical URL that always holds the latest version, eliminating file-name confusion.
Sites improve distribution and navigation: a link moves frictionlessly across email, Slack, and CRMs, and allows readers to jump to relevant sections rather than reading linearly.
AI coding tools like Codex's new 'Sites' feature make it as easy to build a polished web app as to create a deck, lowering the barrier for non-developers.
Websites enable observability—knowing what got clicked, read, or abandoned—which is impossible with a PDF or deck sent into the void.
Host suggests 18 specific use cases, including shifting from slide decks to narrative websites, from spreadsheets to data dashboards, and from static training PDFs to dynamic learning hubs.
"For decades, knowledge workers have packaged thinking into different types of documents. The menu of formats wasn't chosen because they were the best way to carry knowledge, but because the ability to use code was limited to a very specific few."
"A URL fixes the update versioning problem. It gives knowledge a canonical home—whenever people land on that URL, it is the most up-to-date version."
"Coding agents are basically solved at this point. But coding is maybe a quarter of an engineer's actual day. The rest is standups, stakeholder updates, meeting prep, chasing contacts across six different tools."