10+ Things You Should Build With AI Instead of Sending Files

Today on the AI Daily Brief, 10 or 15 or even 20 sites that knowledge workers should build with AI. The AI Daily Brief is a daily podcast and video about the most important news and discussions in AI. Alrighty, friends. Quick announcements before we dive in. First of all, thank you to today's sponsors, Robots and Pencils, Assembly, ZenCoder, and OutSystems. To get an ad free version of the show, go to patreon.com/aidailybrief, or you can, of course, subscribe on Apple Podcasts. To learn more about sponsoring the show, send us a note at sponsors@aidailybrief.ai.aidailybrief.ai is also where you can find out about other things going on in the ecosystem. For example, one more call to sign up for the four week sprint executive catch up program. This is being led by Nufar Gaspar, and she gave a bit of a preview on our episode a couple of weeks ago. If you have been feeling behind in practice and wanna be up to speed and moving ahead, this could be the program for you. Registration is closing in the next day or so, so check it out at aiexecutivecatchup.com. Obviously, that link will be in the show notes as well. Now happy weekend, friends. It being a weekend, this is, of course, a long read style or big think episode. Although today, we're gonna do something a bit more practical that was inspired directly by a launch from this week. On Tuesday, OpenAI announced a bunch of updates to codecs. One of them is called sites. And effectively, sites is just a simplified way to take the things that you're building with codecs and publish them as a website or a web app that your team or friends or colleagues can interact with. I think the idea is, whereas in the past to actually publish something, you'd either need to have a hosting platform like Vercel and a database platform like Supabase and wire that together with Cloud Code or codecs or alternately be using an all in one Vibe code experience like Replitter Lovable. Now that sort of all in one experience is native to codex, simplifying the whole process. Now one of the things that I think this both recognizes but also amplifies is the idea of the website or simple web app as a new unit of work output, I e a new anchor artifact in the knowledge workers toolkit. Now for decades, knowledge workers have packaged thinking into different types of documents, decks, spreadsheets, PDFs, email threads, shared folders, etcetera, whatever the menu of formats available was. Importantly though, that menu wasn't chosen because the formats were the best way to carry knowledge necessarily, but the ability to use code to turn those artifacts into something more interactive, dynamic, updatable was limited to a very specific few, and the literal cost in terms of money or distraction of other people in the company meant that a website wasn't really on the table as a format. …